From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: rppt@kernel.org, peterz@infradead.org, akpm@linux-foundation.org,
david@kernel.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, linux-mm@kvack.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, stable@vger.kernel.org,
4ncienth@gmail.com, alexander.motin@truenas.com,
caleb.stjohn@truenas.com, ameer.hamza@truenas.com
Subject: Re: [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs
Date: Fri, 9 Oct 2026 12:56:57 +0100 [thread overview]
Message-ID: <asjWUyFVbq4fhfLu@gremlin> (raw)
In-Reply-To: <2026-10-04-1-daily-reply-0001-secretmem-requeue@kernel.org>
On Sun, Oct 04, 2026 at 12:29:39PM -0400, Sasha Levin wrote:
> > Since commit 97d34aa65c29 ("mm/secretmem: properly account locked
> > pages"), in v7.3-rc2 and the 6.18.52 and 7.2.5 backports, touching a
> > memfd_secret() page for the first time fails with SIGBUS while the
> > same user is running perf record, and read() into such a page fails
> > with EFAULT.
>
> Re-queued the secretmem accounting fix for 6.12, 6.6 and 6.1, per Lorenzo.
> The perf fix will be needed on these trees once it lands.
Thanks!
Perf fix sent at [0], LPC will be slowing everybody down though I expect!
--
Cheers, Lorenzo
[0]:https://lore.kernel.org/all/20261003-perf-locked-vm-fix-v1-1-d214dcaf0d76@kernel.org/
prev parent reply other threads:[~2026-10-09 11:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 17:56 [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs Ameer Hamza
2026-10-03 1:30 ` Sasha Levin
2026-10-03 9:18 ` Lorenzo Stoakes (ARM)
2026-10-03 14:30 ` Sasha Levin
2026-10-03 16:23 ` Lorenzo Stoakes (ARM)
2026-10-03 22:34 ` Sasha Levin
2026-10-03 14:14 ` David Hildenbrand (Arm)
2026-10-03 17:05 ` Ameer Hamza
2026-10-05 10:38 ` David Hildenbrand (Arm)
2026-10-03 15:56 ` Lorenzo Stoakes (ARM)
2026-10-03 16:31 ` Lorenzo Stoakes (ARM)
2026-10-03 18:02 ` Ameer Hamza
2026-10-04 16:29 ` Sasha Levin
2026-10-09 11:56 ` Lorenzo Stoakes (ARM) [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=asjWUyFVbq4fhfLu@gremlin \
--to=ljs@kernel.org \
--cc=4ncienth@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.motin@truenas.com \
--cc=ameer.hamza@truenas.com \
--cc=caleb.stjohn@truenas.com \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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.