From: Emanuele Rocca <emanuele.rocca@arm.com>
To: Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [BUG] ARM64 regression: NULL pointer dereference in arm_smccc_version_init+0x90/0x1ac
Date: Thu, 6 Feb 2025 17:57:41 +0100 [thread overview]
Message-ID: <Z6TqBQKSILZUnYbJ@NH27D9T0LF> (raw)
In-Reply-To: <20250206131154.GD3204@willie-the-truck>
On 2025-02-06 01:11, Will Deacon wrote:
> In your screenshot, x6 looks like it's retained its poison value, but
> that was the register being corrupted in the initial report. Maybe you
> could share the diff you made?
Sure, please see [1]. A kernel built with that patch crashes and all
registers retain their poison values.
I now also tried moving the poisoning before the smccc_version /
smccc_conduit assignments, and the resulting kernel does *not* crash.
See [2].
[1] https://people.debian.org/~ema/w1-w17-crash.diff
[2] https://people.debian.org/~ema/w1-w17-nocrash.diff
next prev parent reply other threads:[~2025-02-06 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 14:52 [BUG] ARM64 regression: NULL pointer dereference in arm_smccc_version_init+0x90/0x1ac Emanuele Rocca
2025-01-30 11:43 ` Will Deacon
2025-02-05 10:35 ` Emanuele Rocca
2025-02-06 13:08 ` Will Deacon
2025-01-30 12:19 ` Mark Rutland
2025-01-30 14:56 ` Emanuele Rocca
2025-01-31 12:41 ` Will Deacon
2025-01-31 13:54 ` Mark Rutland
2025-02-04 10:00 ` Will Deacon
2025-02-05 16:50 ` Emanuele Rocca
2025-02-06 13:11 ` Will Deacon
2025-02-06 16:57 ` Emanuele Rocca [this message]
2025-03-13 22:08 ` Will Deacon
2025-09-26 10:36 ` Dan Carpenter
2025-09-26 11:03 ` Will Deacon
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=Z6TqBQKSILZUnYbJ@NH27D9T0LF \
--to=emanuele.rocca@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.