From: "Dong, Eric" <eric.dong@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH v3 0/2] UefiCpuPkg: [CVE-2017-5715] Stuff RSB before RSM
Date: Mon, 20 Aug 2018 06:46:32 +0000 [thread overview]
Message-ID: <ED077930C258884BBCB450DB737E66224AC92B8B@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20180817023511.6420-1-hao.a.wu@intel.com>
Reviewed-by: Eric Dong <eric.dong@intel.com> for this serial.
> -----Original Message-----
> From: Wu, Hao A
> Sent: Friday, August 17, 2018 10:35 AM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A <hao.a.wu@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>;
> Dong, Eric <eric.dong@intel.com>; Laszlo Ersek <lersek@redhat.com>; Kinney,
> Michael D <michael.d.kinney@intel.com>
> Subject: [PATCH v3 0/2] UefiCpuPkg: [CVE-2017-5715] Stuff RSB before RSM
>
> V3 changes:
> A. Add relating CVE issue number to the commits' subject line.
>
> B. Keep the URL links within log messages unwrapped.
>
> C. Add TianoCore Bugzilla link reference to each commits.
>
> D. Mention further actions should be taken after pushing the series in log
> messages.
>
> E. Refine file description comments for StuffRsb.inc files.
>
> V2 changes:
> A. Refine commit log message to clarify the purpose of the series
>
> B. Extract the RSB stuffing logic to INC files to avoid code duplication:
> When compiling .NASM source files, the current build rule does not support
> including files other than the .NASM file directory, this series will duplicate
> the StuffRsb.inc file together with the .NASM files at this moment.
>
> Please consider this approach as the first stage, I have filed a Bugzilla for
> adding $(INC)-like support when compiling .NASM files:
> https://bugzilla.tianocore.org/show_bug.cgi?id=1085
>
> After the above support is added, the next step will be taken to remove those
> duplicated StuffRsb.inc files and put it under a common include directory like:
> UefiCpuPkg/Include/
>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>
> Hao Wu (2):
> UefiCpuPkg/PiSmmCpuDxeSmm: [CVE-2017-5715] Stuff RSB before RSM
> UefiCpuPkg/SmmCpuFeaturesLib: [CVE-2017-5715] Stuff RSB before RSM
>
> UefiCpuPkg/Library/SmmCpuFeaturesLib/Ia32/SmiEntry.nasm | 3 ++
> UefiCpuPkg/Library/SmmCpuFeaturesLib/Ia32/SmiException.nasm | 10 ++--
> UefiCpuPkg/Library/SmmCpuFeaturesLib/Ia32/StuffRsb.inc | 55
> ++++++++++++++++++++
> UefiCpuPkg/Library/SmmCpuFeaturesLib/X64/SmiEntry.nasm | 3 ++
> UefiCpuPkg/Library/SmmCpuFeaturesLib/X64/SmiException.nasm | 8 ++-
> UefiCpuPkg/Library/SmmCpuFeaturesLib/X64/StuffRsb.inc | 55
> ++++++++++++++++++++
> UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmiEntry.nasm | 3 ++
> UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmInit.nasm | 3 ++
> UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/StuffRsb.inc | 55
> ++++++++++++++++++++
> UefiCpuPkg/PiSmmCpuDxeSmm/X64/SmiEntry.nasm | 3 ++
> UefiCpuPkg/PiSmmCpuDxeSmm/X64/SmmInit.nasm | 3 ++
> UefiCpuPkg/PiSmmCpuDxeSmm/X64/StuffRsb.inc | 55
> ++++++++++++++++++++
> 12 files changed, 251 insertions(+), 5 deletions(-) create mode 100644
> UefiCpuPkg/Library/SmmCpuFeaturesLib/Ia32/StuffRsb.inc
> create mode 100644
> UefiCpuPkg/Library/SmmCpuFeaturesLib/X64/StuffRsb.inc
> create mode 100644 UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/StuffRsb.inc
> create mode 100644 UefiCpuPkg/PiSmmCpuDxeSmm/X64/StuffRsb.inc
>
> --
> 2.12.0.windows.1
prev parent reply other threads:[~2018-08-20 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 2:35 [PATCH v3 0/2] UefiCpuPkg: [CVE-2017-5715] Stuff RSB before RSM Hao Wu
2018-08-17 2:35 ` [PATCH v3 1/2] UefiCpuPkg/PiSmmCpuDxeSmm: " Hao Wu
2018-08-17 12:01 ` Laszlo Ersek
2018-08-17 2:35 ` [PATCH v3 2/2] UefiCpuPkg/SmmCpuFeaturesLib: " Hao Wu
2018-08-20 6:46 ` Dong, Eric [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=ED077930C258884BBCB450DB737E66224AC92B8B@shsmsx102.ccr.corp.intel.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