From: Ameer Hamza <ameer.hamza@truenas.com>
To: "Lorenzo Stoakes (ARM)" <ljs@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, 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: Sat, 3 Oct 2026 23:02:24 +0500 [thread overview]
Message-ID: <asFC2Oryo2-9ww5r@hamza-PC> (raw)
In-Reply-To: <asEllR7if-J3wteg@gremlin>
On Sat, Oct 03, 2026 at 04:56:32PM +0100, Lorenzo Stoakes (ARM) wrote:
> So this is a bug in perf, which should use its own counter for this,
> AFAICT.
Agreed, and the report's closing question pointed the same way, since
the commit itself closes a real hole. Glad the longstanding perf bug is
getting fixed as a result. Thanks for the analysis and for turning the
fix around so quickly.
Thanks,
Ameer Hamza
next prev parent reply other threads:[~2026-10-03 18:02 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 [this message]
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=asFC2Oryo2-9ww5r@hamza-PC \
--to=ameer.hamza@truenas.com \
--cc=4ncienth@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.motin@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=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.