[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE8VWiJ62xT9shaEmUTOPF1OAztaWsr57m-wY9jyMJt5WFke5g@mail.gmail.com>
Date: Tue, 19 Nov 2024 22:05:35 +0530
From: Shresth Prasad <shresthprasad7@...il.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: x86@...nel.org, Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/sev: Fix dereference NULL return value
On Tue, Nov 19, 2024 at 5:33 PM Markus Elfring <Markus.Elfring@....de> wrote:
>
> > Skip to the next CPU if `pte` is assigned NULL by `lookup_address`
>
> a null pointer was returned by a lookup_address() call.
>
>
> * How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
For the Fixes tag, I'm not sure which commit hash I should put. Should I use
the commit where the function was introduced?
>
> * Would a summary phrase like “Prevent null pointer dereference in snp_kexec_finish()”
> be a bit nicer?
You're right, I'll change the phrasing. Thank you for the feedback.
Best Regards,
Shresth
Powered by blists - more mailing lists