From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lersek@redhat.com>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com;
 receiver=edk2-devel@lists.01.org 
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ml01.01.org (Postfix) with ESMTPS id 037C02194D3AE
 for <edk2-devel@lists.01.org>; Mon, 22 Oct 2018 01:30:57 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com
 [10.5.11.22])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id 6296413A82;
 Mon, 22 Oct 2018 08:30:56 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-121-1.rdu2.redhat.com
 [10.10.121.1])
 by smtp.corp.redhat.com (Postfix) with ESMTP id 0077B105704E;
 Mon, 22 Oct 2018 08:30:54 +0000 (UTC)
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>
References: <1539655573-5456-1-git-send-email-liming.gao@intel.com>
 <a9b25c6f-d0e2-11a4-bb37-4e4871178203@intel.com>
 <b367b5d9-1bc9-ffdf-79a6-f3a54c040b2d@redhat.com>
 <4A89E2EF3DFEDB4C8BFDE51014F606A14E33D7CF@SHSMSX104.ccr.corp.intel.com>
 <155ff850-d652-30c9-5c02-7f1412a8f079@redhat.com>
 <4A89E2EF3DFEDB4C8BFDE51014F606A14E33DD17@SHSMSX104.ccr.corp.intel.com>
 <860c2c8f-c026-5873-0405-131a40a133aa@redhat.com>
 <4A89E2EF3DFEDB4C8BFDE51014F606A14E3462C0@SHSMSX104.ccr.corp.intel.com>
From: Laszlo Ersek <lersek@redhat.com>
Message-ID: <5a832d8c-f0bd-3c1a-803f-4c86dbc1388b@redhat.com>
Date: Mon, 22 Oct 2018 10:30:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3462C0@SHSMSX104.ccr.corp.intel.com>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.5.110.29]); Mon, 22 Oct 2018 08:30:56 +0000 (UTC)
Subject: Re: [Patch 0/3] Add more checker for Tianocompress and Ueficompress
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 08:30:58 -0000
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

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