public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrei Warkentin" <andrei.warkentin@intel.com>
To: Leif Lindholm <quic_llindhol@quicinc.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	Andrew Fish <afish@apple.com>
Cc: "Li, Yong" <yong.li@intel.com>,
	Sunil V L <sunilvl@ventanamicro.com>,
	"Tuan Phan" <tphan@ventanamicro.com>,
	Daniel Schaefer <git@danielschaefer.me>
Subject: Re: [edk2-devel] [PATCH v1 1/1] RISCV: Fix InternalLongJump to return correct value
Date: Tue, 19 Sep 2023 16:14:48 +0000	[thread overview]
Message-ID: <PH8PR11MB6856D98A15F3FC83C2B1F87283FAA@PH8PR11MB6856.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6b5d732e-fe65-44c0-b63a-f4320846da9e@quicinc.com>

Thanks Leif, this unfortunate inclusion has already been remedied in the v2. What happens is that random files in the tree get changed by virtue of just doing a build, so it is very easy to accidentally pull it in. And it's a single line that I missed manually looking over the patch.

Wrt license inclusion, I'm just aping what everyone else appears to do. My personal two cents is that the whole thing is rather silly - the code ought to be entirely owned by Tiano, but if other vendors are going to add Copyrights - all of them might as well. I'd rather this discussion be taken separately from fixing this rather critical issue, and ideally bubbled up to Tiano leadership.

A

> -----Original Message-----
> From: Leif Lindholm <quic_llindhol@quicinc.com>
> Sent: Tuesday, September 19, 2023 9:41 AM
> To: Ard Biesheuvel <ardb@kernel.org>; devel@edk2.groups.io; Warkentin,
> Andrei <andrei.warkentin@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Andrew Fish <afish@apple.com>
> Cc: Li, Yong <yong.li@intel.com>; Sunil V L <sunilvl@ventanamicro.com>; Tuan
> Phan <tphan@ventanamicro.com>; Daniel Schaefer <git@danielschaefer.me>
> Subject: Re: [edk2-devel] [PATCH v1 1/1] RISCV: Fix InternalLongJump to return
> correct value
> 
> On 2023-09-19 15:31, Ard Biesheuvel wrote:
> > Hello Andrei,
> >
> > On Tue, 19 Sept 2023 at 04:43, Andrei Warkentin
> > <andrei.warkentin@intel.com> wrote:
> >>
> >> InternalLongJump was not returning the 2nd parameter passed to
> >> LongJmp (Value) as the return value from SetJmp.
> >>
> >> Seen with code compiled with -Os, where an LongJmp (Buffer, -1)
> >> somehow translated to SetJmp returning 0...
> >>
> >> Cc: Yong Li <yong.li@intel.com>
> >> Cc: Sunil V L <sunilvl@ventanamicro.com>
> >> Cc: Tuan Phan <tphan@ventanamicro.com>
> >> Cc: Daniel Schaefer <git@danielschaefer.me>
> >> Signed-off-by: Andrei Warkentin <andrei.warkentin@intel.com>
> >> ---
> >>   CryptoPkg/Library/OpensslLib/openssl                  | 2 +-
> >>   MdePkg/Library/BaseLib/RiscV64/RiscVSetJumpLongJump.S | 7 ++-----
> >>   2 files changed, 3 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/CryptoPkg/Library/OpensslLib/openssl
> >> b/CryptoPkg/Library/OpensslLib/openssl
> >> index de90e54bbe82..830bf8e1e474 160000
> >> --- a/CryptoPkg/Library/OpensslLib/openssl
> >> +++ b/CryptoPkg/Library/OpensslLib/openssl
> >> @@ -1 +1 @@
> >> -Subproject commit de90e54bbe82e5be4fb9608b6f5c308bb837d355
> >> +Subproject commit 830bf8e1e4749ad65c51b6a1d0d769ae689404ba
> >
> > This does not belong here
> >
> >> diff --git a/MdePkg/Library/BaseLib/RiscV64/RiscVSetJumpLongJump.S
> >> b/MdePkg/Library/BaseLib/RiscV64/RiscVSetJumpLongJump.S
> >> index 34486eabba4c..e97a7d0727b8 100644
> >> --- a/MdePkg/Library/BaseLib/RiscV64/RiscVSetJumpLongJump.S
> >> +++ b/MdePkg/Library/BaseLib/RiscV64/RiscVSetJumpLongJump.S
> >> @@ -3,6 +3,7 @@
> >>   // Set/Long jump for RISC-V
> >>   //
> >>   // Copyright (c) 2020, Hewlett Packard Enterprise Development LP.
> >> All rights reserved.<BR>
> >> +// Copyright (c) 2023, Intel Corporation. All rights reserved.<BR>
> >
> > I suppose there is some internal policy at Intel that tells you to
> > claim copyright, but do you really think fixing existing HP code by
> > removing 4 instructions and adding one back is sufficient for claiming
> > copyright on the entire file?
> >
> > Note that I am not objecting to this in principle: I am just curious
> > (and I have objected in the past to patches that only removed lines
> > from existing code and then added a copyright line)
> >
> > Should we have some project/community wide guidance on this?
> 
> I reacted early on when joining this project that copyright was frequently
> added/bumped for trivial changes, including things like fixing typos in
> comments. So I think the custom for this project is that the bar is a lot lower
> than for projects like Linux, grub, etc.
> 
> So I see this as on par for tianocore.
> 
> > (The problem is that claiming copyright gives the right to distribute
> > the code without being bound by the terms of the license)
> 
> Wouldn't all the other copyright holders also need to agree?
> 
> /
>      Leif
> 
> >>   //
> >>   // SPDX-License-Identifier: BSD-2-Clause-Patent
> >>   //
> >> @@ -47,9 +48,5 @@ InternalLongJump:
> >>       REG_L s10, 11*SZREG(a0)
> >>       REG_L s11, 12*SZREG(a0)
> >>       REG_L sp,  13*SZREG(a0)
> >> -
> >> -    add   a0, s0, 0
> >> -    add   a1, s1, 0
> >> -    add   a2, s2, 0
> >> -    add   a3, s3, 0
> >> +    mv    a0, a1
> >>       ret
> >> --
> >> 2.34.1
> >>
> >>
> >>
> >> 
> >>
> >>



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108850): https://edk2.groups.io/g/devel/message/108850
Mute This Topic: https://groups.io/mt/101450445/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2023-09-19 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  4:43 [edk2-devel] [PATCH v1 0/1] RISCV: Fix InternalLongJump Andrei Warkentin
2023-09-19  4:43 ` [edk2-devel] [PATCH v1 1/1] RISCV: Fix InternalLongJump to return correct value Andrei Warkentin
2023-09-19  8:01   ` Yao, Jiewen
2023-09-19  8:04     ` Andrei Warkentin
2023-09-19 14:31   ` Ard Biesheuvel
2023-09-19 14:41     ` Leif Lindholm
2023-09-19 16:14       ` Andrei Warkentin [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=PH8PR11MB6856D98A15F3FC83C2B1F87283FAA@PH8PR11MB6856.namprd11.prod.outlook.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