From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross boundary access in Ramdisk
Date: Thu, 28 Feb 2019 12:52:34 +0100 [thread overview]
Message-ID: <202bf29c-a445-d8fd-0b3a-e2ed83c57866@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3F44B7@SHSMSX104.ccr.corp.intel.com>
On 02/28/19 02:32, Gao, Liming wrote:
> I update https://github.com/tianocore/tianocore.github.io/wiki/Commit-Message-Format with CVE example. Please check it.
"CVE fix needs to append CVE number in Brief-single-line-summary. The
format is 'Pkg-Module: Brief-single-line-summary (CVE-Year-Number)'. Its
length should be less than 92 characters."
Let's use the following suffix as example:
" (CVE-2018-12180)"
(the Number part is supposed to fit into 5 digits)
The length of this suffix is 17 characters. For normal cases, we have an
inclusive limit of 74 characters. So for CVE subjects the inclusive
limit is 74+17=91 characters. The wiki page states an exclusive limit of
92 chars, which is the same.
So, I think the update is perfect.
Thanks
Laszlo
prev parent reply other threads:[~2019-02-28 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 7:45 [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross boundary access in Ramdisk Hao Wu
2019-02-26 7:45 ` [PATCH v2 1/2] MdeModulePkg/PartitionDxe: Ensure blocksize can hold MBR (CVE FIX) Hao Wu
2019-02-26 7:45 ` [PATCH v2 2/2] MdeModulePkg/RamDiskDxe: Ramdisk size be multiple of BlkSize " Hao Wu
2019-02-26 11:45 ` [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross boundary access in Ramdisk Laszlo Ersek
2019-02-26 12:57 ` Wu, Hao A
2019-02-27 6:56 ` Wu, Hao A
2019-02-27 8:58 ` Laszlo Ersek
2019-02-27 12:49 ` Gao, Liming
2019-02-27 19:30 ` Laszlo Ersek
2019-02-28 1:32 ` Gao, Liming
2019-02-28 11:52 ` 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=202bf29c-a445-d8fd-0b3a-e2ed83c57866@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