From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Ameer Hamza <ameer.hamza@truenas.com>
Cc: ljs@kernel.org, rppt@kernel.org, peterz@infradead.org,
akpm@linux-foundation.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, sashal@kernel.org,
alexander.motin@truenas.com, caleb.stjohn@truenas.com
Subject: Re: [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs
Date: Mon, 5 Oct 2026 12:38:09 +0200 [thread overview]
Message-ID: <d286ba75-c89c-4b34-8447-e1d9eeb2d515@kernel.org> (raw)
In-Reply-To: <asE0ctESLO306qYs@hamza-PC>
On 10/3/26 19:05, Ameer Hamza wrote:
> On Sat, Oct 03, 2026 at 04:14:49PM +0200, David Hildenbrand (Arm) wrote:
>> May I know whether this problem was found by
>>
>> (a) A real workload
>>
>> (b) A test case
>>
>> (c) Complains by some tooling
>
> (a). A root userspace process that keeps secrets in memfd_secret()
> failed while perf record ran on the same machine. I reduced it to the
> snippet in the report.
Thanks!
--
Cheers,
David
next prev parent reply other threads:[~2026-10-05 10:38 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) [this message]
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)
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=d286ba75-c89c-4b34-8447-e1d9eeb2d515@kernel.org \
--to=david@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=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=ljs@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.