public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zeng, Star" <star.zeng@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH 0/2] MdeModulePkg/UsbBusPei: validate HW data before using
Date: Fri, 26 Oct 2018 02:45:45 +0000	[thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103BC5BA2E@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20181025101122.233308-1-ruiyu.ni@intel.com>

Reviewed-by: Star Zeng <star.zeng@intel.com>

As I know, you did Recovery test with USB disk for these patches.
I think you can add the test information into the commit message of patches.


Thanks,
Star
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ruiyu Ni
Sent: Thursday, October 25, 2018 6:11 PM
To: edk2-devel@lists.01.org
Subject: [edk2] [PATCH 0/2] MdeModulePkg/UsbBusPei: validate HW data before using

The patches sync the similar fixes to UsbBusDxe to UsbBusPei.

Ruiyu Ni (2):
  MdeModulePkg/UsbBusPei: Fix out-of-bound read access to descriptors
  MdeModulePkg/UsbBusPei: Reject descriptor whose length is bad

 MdeModulePkg/Bus/Usb/UsbBusPei/UsbPeim.c | 93 +++++++++++++++++++-------------  MdeModulePkg/Bus/Usb/UsbBusPei/UsbPeim.h | 11 ++++
 2 files changed, 67 insertions(+), 37 deletions(-)

--
2.16.1.windows.1

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2018-10-26  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 10:11 [PATCH 0/2] MdeModulePkg/UsbBusPei: validate HW data before using Ruiyu Ni
2018-10-25 10:11 ` [PATCH 1/2] MdeModulePkg/UsbBusPei: Fix out-of-bound read access to descriptors Ruiyu Ni
2018-10-25 10:11 ` [PATCH 2/2] MdeModulePkg/UsbBusPei: Reject descriptor whose length is bad Ruiyu Ni
2018-10-26  2:45 ` Zeng, Star [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=0C09AFA07DD0434D9E2A0C6AEB0483103BC5BA2E@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