From: Laszlo Ersek <lersek@redhat.com>
To: Hao Wu <hao.a.wu@intel.com>, edk2-devel@lists.01.org
Cc: Jiewen Yao <jiewen.yao@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [PATCH v3 0/5] [CVE-2017-5753] Bounds Check Bypass issue in SMI handlers
Date: Sat, 29 Sep 2018 19:33:32 +0200 [thread overview]
Message-ID: <77bd9e44-6b9d-be19-748f-41a22c41f498@redhat.com> (raw)
In-Reply-To: <20180929065736.12796-1-hao.a.wu@intel.com>
On 09/29/18 08:57, Hao Wu wrote:
> V3 changes:
> A. Fix wrong file (should be LoadFenceSmm.c) gets listed in
> MdeModulePkg/Universal/Variable/RuntimeDxe/VariableSmm.inf
>
> B. Rename the newly introduced internal function from 'VariableLoadFence'
> to 'MemoryLoadFence' within
> MdeModulePkg/Universal/Variable/RuntimeDxe/
>
> C. Remove extra empty line before EOF for files:
> MdePkg/Library/BaseLib/Ia32/Lfence.nasm
> MdePkg/Library/BaseLib/X64/Lfence.nasm
>
> D. Remove dummy message within commit log messages
>
> Since A. has functional impact. Thus send V3 of the series.
series
Acked-by: Laszlo Ersek <lersek@redhat.com>
Regression-tested-by: Laszlo Ersek <lersek@redhat.com>
Thanks
Laszlo
next prev parent reply other threads:[~2018-09-29 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 6:57 [PATCH v3 0/5] [CVE-2017-5753] Bounds Check Bypass issue in SMI handlers Hao Wu
2018-09-29 6:57 ` [PATCH v3 1/5] MdePkg/BaseLib: Add new AsmLfence API Hao Wu
2018-09-29 6:57 ` [PATCH v3 2/5] MdeModulePkg/FaultTolerantWrite:[CVE-2017-5753]Fix bounds check bypass Hao Wu
2018-09-29 6:57 ` [PATCH v3 3/5] MdeModulePkg/SmmLockBox: [CVE-2017-5753] Fix " Hao Wu
2018-09-29 6:57 ` [PATCH v3 4/5] MdeModulePkg/Variable: " Hao Wu
2018-09-29 6:57 ` [PATCH v3 5/5] UefiCpuPkg/PiSmmCpuDxeSmm: " Hao Wu
2018-09-29 17:33 ` Laszlo Ersek [this message]
2018-09-30 5:20 ` [PATCH v3 0/5] [CVE-2017-5753] Bounds Check Bypass issue in SMI handlers Wu, Hao A
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=77bd9e44-6b9d-be19-748f-41a22c41f498@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