From: Will Deacon <will@kernel.org>
To: Brian Ruley <brian.ruley@gehealthcare.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Steve Capper <steve.capper@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com
Subject: Re: [PATCH] mm/arm: pgtable: remove young bit check for pte_valid_user
Date: Tue, 14 Apr 2026 12:08:42 +0100 [thread overview]
Message-ID: <ad4gOu83zY-SKijx@willie-the-truck> (raw)
In-Reply-To: <ad3wRQt7K-QLX8Jw@zoo11.fihel.lab.ge-healthcare.net>
On Tue, Apr 14, 2026 at 10:44:05AM +0300, Brian Ruley wrote:
> On Apr 13, Brian Ruley wrote:
> >
> > In the meanwhile, I'll see if I can add some instrumentation to
> > verify this is the bug we're seeing.
>
> The instrumentation worked (used the same ring buffer approach to track
> dcache flushes). Here's the output:
>
> ```
> kernel: [48629.557043] SIGILL at b6b80ac0 cpu 1 pid 32663 linux_pte=8eff659f hw_pte=8eff6e7e young=1 exec=1
> kernel: [48629.557157] dcache flush START cpu0 pfn=8eff6 ts=48629557020154
> kernel: [48629.557207] dcache flush FINISH cpu0 pfn=8eff6 ts=48629557036154
> kernel: [48629.557230] dcache flush SKIPPED cpu1 pfn=8eff6 ts=48629557020154
> audisp-syslog: type=ANOM_ABEND msg=audit(1776154637.460:15): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=32663 comm="journalctl" exe="/usr/bin/journalctl" sig=4 res=1 AUID="unset" UID="root" GID="root"
> ```
Red-handed!
Please send a patch for review (perhaps you can include that snippet in
the commit message).
Cheers,
Will
next prev parent reply other threads:[~2026-04-14 11:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 12:54 [PATCH] mm/arm: pgtable: remove young bit check for pte_valid_user Brian Ruley
2026-04-09 13:56 ` Will Deacon
2026-04-09 14:21 ` Russell King (Oracle)
2026-04-09 14:43 ` Russell King (Oracle)
2026-04-09 15:17 ` Brian Ruley
2026-04-09 16:00 ` Russell King (Oracle)
2026-04-10 11:01 ` Brian Ruley
2026-04-10 11:18 ` Russell King (Oracle)
2026-04-10 11:43 ` [RFC PATCH] test: " Brian Ruley
2026-04-13 10:58 ` [PATCH] " Will Deacon
2026-04-13 11:17 ` Brian Ruley
2026-04-13 14:42 ` Russell King (Oracle)
2026-04-13 15:24 ` Brian Ruley
2026-04-14 6:28 ` Brian Ruley
2026-04-14 7:44 ` Brian Ruley
2026-04-14 11:08 ` Will Deacon [this message]
2026-04-14 11:43 ` Brian Ruley
2026-04-09 14:15 ` Russell King (Oracle)
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=ad4gOu83zY-SKijx@willie-the-truck \
--to=will@kernel.org \
--cc=brian.ruley@gehealthcare.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=steve.capper@arm.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