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: Wed, 27 Feb 2019 20:30:50 +0100 [thread overview]
Message-ID: <b24d18d3-2806-f7f8-cbdc-aac9d63968f8@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E9CE9@SHSMSX104.ccr.corp.intel.com>
On 02/27/19 13:49, Gao, Liming wrote:
> Laszlo:
> I add my comments.
>
> Thanks
> Liming
>> -----Original Message-----
>> From: Laszlo Ersek [mailto:lersek@redhat.com]
>> Sent: Wednesday, February 27, 2019 4:58 PM
>> To: Wu, Hao A <hao.a.wu@intel.com>; Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
>> Cc: Zeng, Star <star.zeng@intel.com>
>> Subject: Re: [edk2] [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross boundary access in Ramdisk
>>
>> On 02/27/19 07:56, Wu, Hao A wrote:
>>>> -----Original Message-----
>>>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>>>> Laszlo Ersek
>>>> Sent: Tuesday, February 26, 2019 7:45 PM
>>>> To: Wu, Hao A; edk2-devel@lists.01.org
>>>> Cc: Zeng, Star
>>>> Subject: Re: [edk2] [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross
>>>> boundary access in Ramdisk
>>>>
>>>> On 02/26/19 08:45, Hao Wu wrote:
>>>>> V2 changes:
>>>>>
>>>>> Correct CC list information.
>>>>>
>>>>>
>>>>> V1 history:
>>>>>
>>>>> The series will resolve a buffer cross boundary access issue during the
>>>>> use of RAM disks. It is the mitigation for issue CVE-2018-12180.
>>>>>
>>>>> Cc: Jian J Wang <jian.j.wang@intel.com>
>>>>> Cc: Ray Ni <ray.ni@intel.com>
>>>>> Cc: Star Zeng <star.zeng@intel.com>
>>>>>
>>>>> Hao Wu (2):
>>>>> MdeModulePkg/PartitionDxe: Ensure blocksize can hold MBR (CVE FIX)
>>>>> MdeModulePkg/RamDiskDxe: Ramdisk size be multiple of BlkSize (CVE
>>>> FIX)
>>>>>
>>>>> MdeModulePkg/Universal/Disk/RamDiskDxe/RamDiskImpl.h | 6 +++---
>>>>> MdeModulePkg/Universal/Disk/PartitionDxe/Gpt.c | 9 ++++++++-
>>>>> MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c | 9 ++++++++-
>>>>> MdeModulePkg/Universal/Disk/RamDiskDxe/RamDiskBlockIo.c | 20
>>>> ++++++++++++++------
>>>>> MdeModulePkg/Universal/Disk/RamDiskDxe/RamDiskProtocol.c | 5 +++--
>>>>> 5 files changed, 36 insertions(+), 13 deletions(-)
>>>>>
>>>>
>>>> Please put the exact CVE numbers in the subject lines.
>>>
>>> Hello Laszlo and Liming,
>>>
>>> I totally agree the commit subject line should include the CVE number.
>>> But I have one feedback that, if the commit is for a CVE fix, is it
>>> possible to exempt the commit subject from 71 characters limit?
>>
>> In my opinion, that is absolutely the case.
>>
>>> I found it can be hard to summary the commit with the Package/Module plus
>>> the CVE number information.
>>
>> I agree, it is hard. But, IMO, in this case, the precise CVE reference
>> takes priority.
>>
> For this case, I suggest to allow subject line length to be bigger, such as 120 character.
> I will update wiki https://github.com/tianocore/tianocore.github.io/wiki/Commit-Message-Format for CVE commit message format.
> For example: Pkg-Module: Brief-single-line-summary (CVE-Year-Number)
Thanks for that!
Laszlo
next prev parent reply other threads:[~2019-02-27 19:30 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 [this message]
2019-02-28 1:32 ` Gao, Liming
2019-02-28 11:52 ` Laszlo Ersek
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=b24d18d3-2806-f7f8-cbdc-aac9d63968f8@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