From: "Wang, Jian J" <jian.j.wang@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, "Desai, Imran" <imran.desai@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Berger" <stefanb@linux.ibm.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Andrew Fish" <afish@apple.com>,
"Leif Lindholm" <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [PATCH v2 5/5] OvmfPkg: link SM3 support into Tcg2Pei and Tcg2Dxe
Date: Fri, 5 Jul 2019 03:02:55 +0000 [thread overview]
Message-ID: <D827630B58408649ACB04F44C51000362593A38E@SHSMSX107.ccr.corp.intel.com> (raw)
In-Reply-To: <9c92afaf-b368-628e-f686-64257831343b@redhat.com>
Hi Laszlo,
Very sorry for the mistake. I'm totally responsible for it.
Regards,
Jian
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Thursday, July 04, 2019 4:38 AM
> To: Desai, Imran <imran.desai@intel.com>; Wang, Jian J
> <jian.j.wang@intel.com>
> Cc: devel@edk2.groups.io; Justen, Jordan L <jordan.l.justen@intel.com>;
> Ard Biesheuvel <ard.biesheuvel@linaro.org>; Marc-André Lureau
> <marcandre.lureau@redhat.com>; Stefan Berger <stefanb@linux.ibm.com>;
> Cetola, Stephano <stephano.cetola@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Andrew Fish <afish@apple.com>; Leif
> Lindholm <leif.lindholm@linaro.org>
> Subject: Re: [edk2-devel] [PATCH v2 5/5] OvmfPkg: link SM3 support into
> Tcg2Pei and Tcg2Dxe
>
> On 05/28/19 22:40, Imran Desai wrote:
> >
> > BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1781
> >
> > EDK2 Support for SM3 digest algorithm is needed to enable TPM with
> SM3 PCR
> > banks. This digest algorithm is part of the China Crypto algorithm suite.
> > This integration has dependency on the openssl_1_1_1b integration into
> > edk2.
> > This patch links SM3 support into Tcg2Pei and Tcg2Dxe.
> >
> >
> > Signed-off-by: Imran Desai <imran.desai@intel.com>
> > Cc: Jordan Justen <jordan.l.justen@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Cc: Marc-André Lureau <marcandre.lureau@redhat.com>
> > Cc: Stefan Berger <stefanb@linux.ibm.com>
> > ---
> > OvmfPkg/OvmfPkgIa32.dsc | 2 ++
> > OvmfPkg/OvmfPkgIa32X64.dsc | 2 ++
> > OvmfPkg/OvmfPkgX64.dsc | 2 ++
> > 3 files changed, 6 insertions(+)
>
> Wow, what just happened here?
>
> I'm noticing now that this patch has been pushed to the master branch as
> commit a7c7d21ffa9a.
>
> However, *NONE* of the OvmfPkg co-maintainers or reviewers have
> reviewed
> this patch!
>
> The commit message includes "Cc:" lines, but that's a lie. Probably not
> an intentional lie, but a lie nonetheless. These patches have *never*
> been delivered to my inbox, and if I look at the address list on the
> message instance that was reflected by the mailing list, that address
> list confirms the same. I'm pretty sure Imran's git configuration has a
> bug related to CC's. (I've extended the address list now, manually.)
>
> Jian: please revert this patch immediately, stating, as reason, that the
> patch review process was not honored. I'm sorry but I cannot let this
> slide -- if you look at commit a7c7d21ffa9a now, it suggests that the
> OvmfPkg maintainers / reviewers were CC'd (they weren't), but they
> ignored the patch (they didn't -- they couldn't see it), and that
> another maintainer pushed the patch just the same (which is factual, but
> *wrong*).
>
> After the revert, Imran can resubmit the patch, with *functional* CC's,
> and then we can discuss it.
>
> In general, it is fine for one maintainer to push a series that touches
> multiple top-level packages. However, that maintainer *MUST* make sure
> that each patch has sufficient "M" reviews, and he/she is responsible
> for picking up the feedback tags for *all* patches from the list.
>
> Come on now, guys -- have you really known me to be a person that
> *silently ignores* an OvmfPkg patch for more than a month? No
> automated
> out-of-office reply, no "please give me some time to review" reply, just
> silence?
>
> And even if I missed a patch like that, don't you think a maintainer
> deserves a ping first?
>
> ... Why are we, as a community, *still* failing at this process?
>
> Laszlo
>
> > diff --git a/OvmfPkg/OvmfPkgIa32.dsc b/OvmfPkg/OvmfPkgIa32.dsc
> > index 578fc6c98ec8..fb5944aa6945 100644
> > --- a/OvmfPkg/OvmfPkgIa32.dsc
> > +++ b/OvmfPkg/OvmfPkgIa32.dsc
> > @@ -628,6 +628,7 @@ [Components]
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha256/HashInstanceLibSha256.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha384/HashInstanceLibSha384.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha512/HashInstanceLibSha512.
> inf
> > +
> NULL|SecurityPkg/Library/HashInstanceLibSm3/HashInstanceLibSm3.inf
> > }
> > !if $(TPM2_CONFIG_ENABLE) == TRUE
> > SecurityPkg/Tcg/Tcg2Config/Tcg2ConfigDxe.inf
> > @@ -914,5 +915,6 @@ [Components]
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha256/HashInstanceLibSha256.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha384/HashInstanceLibSha384.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha512/HashInstanceLibSha512.
> inf
> > +
> NULL|SecurityPkg/Library/HashInstanceLibSm3/HashInstanceLibSm3.inf
> > }
> > !endif
> > diff --git a/OvmfPkg/OvmfPkgIa32X64.dsc
> b/OvmfPkg/OvmfPkgIa32X64.dsc
> > index eade8f62d3de..64c231f735c2 100644
> > --- a/OvmfPkg/OvmfPkgIa32X64.dsc
> > +++ b/OvmfPkg/OvmfPkgIa32X64.dsc
> > @@ -636,6 +636,7 @@ [Components.IA32]
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha256/HashInstanceLibSha256.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha384/HashInstanceLibSha384.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha512/HashInstanceLibSha512.
> inf
> > +
> NULL|SecurityPkg/Library/HashInstanceLibSm3/HashInstanceLibSm3.inf
> > }
> > !if $(TPM2_CONFIG_ENABLE) == TRUE
> > SecurityPkg/Tcg/Tcg2Config/Tcg2ConfigDxe.inf
> > @@ -924,5 +925,6 @@ [Components.X64]
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha256/HashInstanceLibSha256.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha384/HashInstanceLibSha384.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha512/HashInstanceLibSha512.
> inf
> > +
> NULL|SecurityPkg/Library/HashInstanceLibSm3/HashInstanceLibSm3.inf
> > }
> > !endif
> > diff --git a/OvmfPkg/OvmfPkgX64.dsc b/OvmfPkg/OvmfPkgX64.dsc
> > index 733a4c9d8a43..7e46d401a36f 100644
> > --- a/OvmfPkg/OvmfPkgX64.dsc
> > +++ b/OvmfPkg/OvmfPkgX64.dsc
> > @@ -635,6 +635,7 @@ [Components]
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha256/HashInstanceLibSha256.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha384/HashInstanceLibSha384.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha512/HashInstanceLibSha512.
> inf
> > +
> NULL|SecurityPkg/Library/HashInstanceLibSm3/HashInstanceLibSm3.inf
> > }
> > !if $(TPM2_CONFIG_ENABLE) == TRUE
> > SecurityPkg/Tcg/Tcg2Config/Tcg2ConfigDxe.inf
> > @@ -922,5 +923,6 @@ [Components]
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha256/HashInstanceLibSha256.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha384/HashInstanceLibSha384.
> inf
> >
> NULL|SecurityPkg/Library/HashInstanceLibSha512/HashInstanceLibSha512.
> inf
> > +
> NULL|SecurityPkg/Library/HashInstanceLibSm3/HashInstanceLibSm3.inf
> > }
> > !endif
> >
next prev parent reply other threads:[~2019-07-05 3:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:40 [PATCH v2 0/5] Implement SM3 measured boot Imran Desai
2019-05-28 20:40 ` [PATCH v2 1/5] MdePkg/Protocol/Hash: introduce GUID for SM3 Imran Desai
2019-05-28 20:40 ` [PATCH v2 2/5] SecurityPkg: introduce the SM3 digest algorithm Imran Desai
2019-06-07 22:17 ` [edk2-devel] " Wang, Jian J
2019-05-28 20:40 ` [PATCH v2 3/5] SecurityPkg/HashLibBaseCryptoRouter: recognize " Imran Desai
2019-06-07 22:18 ` [edk2-devel] " Wang, Jian J
2019-05-28 20:40 ` [PATCH v2 4/5] SecurityPkg: set SM3 bit in TPM 2.0 hash mask by default Imran Desai
2019-06-07 22:19 ` [edk2-devel] " Wang, Jian J
2019-05-28 20:40 ` [PATCH v2 5/5] OvmfPkg: link SM3 support into Tcg2Pei and Tcg2Dxe Imran Desai
2019-07-03 20:37 ` [edk2-devel] " Laszlo Ersek
2019-07-03 21:18 ` Leif Lindholm
2019-07-03 22:48 ` Imran Desai
2019-07-04 8:30 ` Laszlo Ersek
2019-07-05 3:02 ` Wang, Jian J [this message]
2019-05-30 4:55 ` [edk2-devel] [PATCH v2 0/5] Implement SM3 measured boot Wang, Jian J
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=D827630B58408649ACB04F44C51000362593A38E@SHSMSX107.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