public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paluri, PavanKumar" <papaluri@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Ashish Kalra <ashish.kalra@amd.com>,
	Michael Roth <michael.roth@amd.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] x86/sev: Fix __reserved field in sev_config
Date: Mon, 29 Jul 2024 18:45:21 -0500	[thread overview]
Message-ID: <dcfc9264-959a-3bb5-95ad-548a6f019430@amd.com> (raw)
In-Reply-To: <20240729193210.GHZqfuOs-t9HuYPF_Y@fat_crate.local>

Hi Boris,

On 7/29/2024 2:32 PM, Borislav Petkov wrote:
> On Mon, Jul 29, 2024 at 01:08:08PM -0500, Pavan Kumar Paluri wrote:
>> sev_config currently has debug, ghcbs_initialized, and use_cas fields.
>> However, __reserved count has not been updated. Fix this.
>>
>> Fixes: 34ff65901735 ("x86/sev: Use kernel provided SVSM Calling Areas")
>> Cc: stable@vger.kernel.org
> 
> stable because?
> 

Thanks for noticing this.

I shall remove Cc tag since:
1. The commit that introduced the bug is only part of 6.11-rc1. So there
is no stable kernel fix needed here.
2. An incorrect __reserved field did not cause any hang/data corruption
or a build-error.

I will re-spin a v2.

Thanks,
Pavan
> 

  reply	other threads:[~2024-07-29 23:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 18:08 [PATCH] x86/sev: Fix __reserved field in sev_config Pavan Kumar Paluri
2024-07-29 19:32 ` Borislav Petkov
2024-07-29 23:45   ` Paluri, PavanKumar [this message]
2024-07-30  5:59     ` Borislav Petkov
2024-07-30  8:24 ` [tip: x86/urgent] " tip-bot2 for Pavan Kumar Paluri
2024-07-30 13:22 ` [PATCH] " Tom Lendacky

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=dcfc9264-959a-3bb5-95ad-548a6f019430@amd.com \
    --to=papaluri@amd.com \
    --cc=ashish.kalra@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=mingo@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.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