From: Will Deacon <will@kernel.org>
To: Mike Galbraith <efault@gmx.de>
Cc: lkml <linux-kernel@vger.kernel.org>, Mark Rutland <mark.rutland@arm.com>
Subject: Re: arm64: perf test 26 rpi4 oops
Date: Fri, 28 Jul 2023 16:23:09 +0100 [thread overview]
Message-ID: <20230728152309.GG21718@willie-the-truck> (raw)
In-Reply-To: <1620591d2201c1498f2832b32d26efd0c5cdd5cf.camel@gmx.de>
On Fri, Jul 28, 2023 at 05:12:43PM +0200, Mike Galbraith wrote:
> On Fri, 2023-07-28 at 15:18 +0100, Will Deacon wrote:
> > On Fri, Jul 28, 2023 at 06:06:33AM +0200, Mike Galbraith wrote:
> > > perf test 26 in virgin master inspired the below.
> >
> > Ah, so this is the 6.5-based panic message below?
>
> Yeah, that was virgin master.
>
> The oops arrived with 2e1c0170771e, _but_ it turns out to be somehow
> config related. The obese distro config rolled forward does not oops,
> much leaner local config does, despite cute little rpi4 working just
> fine.. for everything _except_ 'perf test 26' :)
The commit mentions HARDENED_USERCOPY, so maybe that? In any case, if
you can share your broken config someplace I can try to give it a spin.
Thanks,
Will
next prev parent reply other threads:[~2023-07-28 15:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 4:06 Mike Galbraith
2023-07-28 14:18 ` Will Deacon
2023-07-28 15:12 ` Mike Galbraith
2023-07-28 15:23 ` Will Deacon [this message]
2023-07-28 16:35 ` Mike Galbraith
2023-07-29 16:30 ` Mike Galbraith
2023-07-30 5:54 ` Mike Galbraith
2023-07-30 11:01 ` Mike Galbraith
2023-07-30 16:09 ` Mike Galbraith
2023-07-31 10:43 ` Will Deacon
2023-07-31 11:37 ` Mike Galbraith
2023-07-31 11:52 ` Will Deacon
2023-07-31 16:07 ` Mike Galbraith
2023-07-31 21:08 ` Lorenzo Stoakes
2023-07-31 21:54 ` Lorenzo Stoakes
2023-07-31 23:27 ` Mike Galbraith
2023-07-31 23:48 ` Mike Galbraith
2023-08-01 0:33 ` Mike Galbraith
2023-08-01 4:34 ` Mike Galbraith
2023-08-01 7:27 ` Will Deacon
2023-08-01 8:39 ` Mike Galbraith
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=20230728152309.GG21718@willie-the-truck \
--to=will@kernel.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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
all inboxes | Powered by JetHome®