public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	jason@os.amperecomputing.com,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
	Hanjun Guo <guohanjun@huawei.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Shuai Xue <xueshuai@linux.alibaba.com>,
	Len Brown <lenb@kernel.org>
Subject: Re: Patch "RAS: Report all ARM processor CPER information to userspace" has been added to the 6.18-stable tree
Date: Sun, 14 Dec 2025 20:37:57 -0500	[thread overview]
Message-ID: <aT9mdXWspIz0KXQL@laps> (raw)
In-Reply-To: <20251213111405.65980c34@foz.lan>

On Sat, Dec 13, 2025 at 11:14:05AM +0100, Mauro Carvalho Chehab wrote:
>Hi Sacha,
>
>Em Sat, 13 Dec 2025 04:49:42 -0500
>Sasha Levin <sashal@kernel.org> escreveu:
>
>> This is a note to let you know that I've just added the patch titled
>>
>>     RAS: Report all ARM processor CPER information to userspace
>>
>> to the 6.18-stable tree which can be found at:
>>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>>      ras-report-all-arm-processor-cper-information-to-use.patch
>> and it can be found in the queue-6.18 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>
>You should also backport this patch(*):
>
>	96b010536ee0 efi/cper: align ARM CPER type with UEFI 2.9A/2.10 specs
>
>It fixes a bug at the UEFI parser for the ARM Processor Error record:
>basically, the specs were not clear about how the error type should be
>reported. The Kernel implementation were assuming that this was an
>enum, but UEFI errata 2.9A make it clear that the value is a bitmap.
>
>So, basically, all kernels up to 6.18 are not parsing the field the
>expected way: only "Cache error" was properly reported. The other
>3 types were wrong.
>
>(*) You could need to backport those patches as well:
>
>	a976d790f494 efi/cper: Add a new helper function to print bitmasks
>	8ad2c72e21ef efi/cper: Adjust infopfx size to accept an extra space

Sure, I'll grab those too. Thanks!

-- 
Thanks,
Sasha

      reply	other threads:[~2025-12-15  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251213094943.4133950-1-sashal@kernel.org>
2025-12-13 10:14 ` Patch "RAS: Report all ARM processor CPER information to userspace" has been added to the 6.18-stable tree Mauro Carvalho Chehab
2025-12-15  1:37   ` Sasha Levin [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-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=aT9mdXWspIz0KXQL@laps \
    --to=sashal@kernel.org \
    --cc=bp@alien8.de \
    --cc=guohanjun@huawei.com \
    --cc=jason@os.amperecomputing.com \
    --cc=lenb@kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rafael@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=xueshuai@linux.alibaba.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