From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"Zeng, Star" <star.zeng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Holtsclaw, Brent" <brent.holtsclaw@intel.com>
Subject: Re: [Patch 0/3] Add more checker for Tianocompress and Ueficompress
Date: Mon, 22 Oct 2018 10:30:53 +0200 [thread overview]
Message-ID: <5a832d8c-f0bd-3c1a-803f-4c86dbc1388b@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3462C0@SHSMSX104.ccr.corp.intel.com>
On 10/19/18 16:40, Gao, Liming wrote:
>
> I don't find the detail information for each CVE. BZ 686 attaches one
> doc to list all issues. So, I fix them together. I think one patch is
> allowed to include more than one CVEs. Even if with single CVE, patch
> subject may be longer than 80 characters. If we need strictly follow
> subject length rule, I suggest to mention CVE FIX in subject, and
> list CVE number info in the commit message. User can use git command
> to get full commit log and know which commit is CVE fix. For
> example: MdePkg/UefiDecompressLib: fix potential buffer overflow (CVE
> FIX)
OK.
Thanks!
Laszlo
prev parent reply other threads:[~2018-10-22 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 2:06 [Patch 0/3] Add more checker for Tianocompress and Ueficompress Liming Gao
2018-10-16 2:06 ` [Patch 1/3] MdePkg: Add more checker in UefiDecompressLib to access the valid buffer only Liming Gao
2018-10-16 2:06 ` [Patch 2/3] IntelFrameworkModulePkg: Add more checker in UefiTianoDecompressLib Liming Gao
2018-10-16 2:06 ` [Patch 3/3] BaseTools: Add more checker in Decompress algorithm to access the valid buffer Liming Gao
2018-10-18 12:28 ` Zhu, Yonghong
2018-10-18 3:04 ` [Patch 0/3] Add more checker for Tianocompress and Ueficompress Zeng, Star
2018-10-18 13:02 ` Laszlo Ersek
2018-10-18 13:36 ` Gao, Liming
2018-10-18 16:01 ` Laszlo Ersek
2018-10-19 6:40 ` Gao, Liming
2018-10-19 11:24 ` Laszlo Ersek
2018-10-19 14:40 ` Gao, Liming
2018-10-22 8:30 ` Laszlo Ersek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a832d8c-f0bd-3c1a-803f-4c86dbc1388b@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox