Linux EFI development
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Ard Biesheuvel <ardb@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	<linux-efi@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Zong Li <zong.li@sifive.com>
Subject: Re: [PATCH v6 2/5] riscv: Dump out kernel offset information on panic
Date: Tue, 25 Jul 2023 08:11:43 +0100	[thread overview]
Message-ID: <20230725-clunky-violet-22e909b65bcf@wendy> (raw)
In-Reply-To: <CAHVXubhVOpdZhmENkNbavAYGVZB47K9Q_4GN6RZ+rCex4uBb5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

On Tue, Jul 25, 2023 at 09:05:37AM +0200, Alexandre Ghiti wrote:
> Hi Conor,
> 
> On Mon, Jul 24, 2023 at 4:20 PM Conor Dooley <conor.dooley@microchip.com> wrote:
> >
> > Hey Alex,
> >
> > On Sat, Jul 22, 2023 at 02:38:47PM +0200, Alexandre Ghiti wrote:
> > > Dump out the KASLR virtual kernel offset when panic to help debug kernel.
> > >
> > > Signed-off-by: Zong Li <zong.li@sifive.com>
> >
> > Either you're missing a Co-developed-by: or the author of this patch is
> > incorrect.
> 
> Ok, I thought it would work this way, Zong first did something similar
> a few years ago, so we need his name here. @Palmer Dabbelt if no other
> changes are needed, do you mind replacing the SoB with a
> Co-developed-by?

You can't have a Co-developed-by without a SoB, so both are needed :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-07-25  7:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 12:38 [PATCH v6 0/5] riscv: Introduce KASLR Alexandre Ghiti
2023-07-22 12:38 ` [PATCH v6 1/5] riscv: Introduce virtual kernel mapping KASLR Alexandre Ghiti
2023-07-22 12:38 ` [PATCH v6 2/5] riscv: Dump out kernel offset information on panic Alexandre Ghiti
2023-07-24 14:19   ` Conor Dooley
2023-07-25  7:05     ` Alexandre Ghiti
2023-07-25  7:11       ` Conor Dooley [this message]
2023-07-22 12:38 ` [PATCH v6 3/5] arm64: libstub: Move KASLR handling functions to kaslr.c Alexandre Ghiti
2023-07-24 14:07   ` Ard Biesheuvel
2023-07-22 12:38 ` [PATCH v6 4/5] libstub: Fix compilation warning for rv32 Alexandre Ghiti
2023-07-22 12:38 ` [PATCH v6 5/5] riscv: libstub: Implement KASLR by using generic functions Alexandre Ghiti
2023-07-24 14:31 ` [PATCH v6 0/5] riscv: Introduce KASLR Conor Dooley
2023-07-25  7:08   ` Alexandre Ghiti
2023-08-15 11:24 ` Song Shuai
2023-08-17 13:10   ` Alexandre Ghiti
2023-08-17 13:27     ` Song Shuai
2023-08-30 21:30 ` Sami Tolvanen
2023-08-31  5:33   ` Conor Dooley
2023-09-06 23:27   ` Charlie Jenkins

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-all 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=20230725-clunky-violet-22e909b65bcf@wendy \
    --to=conor.dooley@microchip.com \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=zong.li@sifive.com \
    /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