From: Steven Rostedt <rostedt@goodmis.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
"Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
"mchehab+huawei@kernel.org" <mchehab+huawei@kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"xieyuanbin1@huawei.com" <xieyuanbin1@huawei.com>,
"Lai, Yi1" <yi1.lai@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: mm/memory-failure tracepoint change breaks userspace rasdaemon
Date: Wed, 3 Jun 2026 15:31:15 -0400 [thread overview]
Message-ID: <20260603153115.775a2e81@fedora> (raw)
In-Reply-To: <b637ede2-73da-49f0-a7eb-70ec79e79624@kernel.org>
On Wed, 3 Jun 2026 21:13:30 +0200
"David Hildenbrand (Arm)" <david@kernel.org> wrote:
> Thanks, that makes sense!
>
> So, would it be fair to say that, in general, what's exposed through
>
> /sys/kernel/tracing/events/
>
> is stable ABI?
It's only stable if something depends on it. It changes all the time.
It's only when someone complains about it that it becomes "stable"!
-- Steve
next prev parent reply other threads:[~2026-06-03 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CY8PR11MB7134346A3E4BB28ECA28D6E989132@CY8PR11MB7134.namprd11.prod.outlook.com>
2026-06-03 13:44 ` mm/memory-failure tracepoint change breaks userspace rasdaemon David Hildenbrand (Arm)
2026-06-03 16:17 ` Steven Rostedt
2026-06-03 16:19 ` Borislav Petkov
2026-06-03 16:26 ` David Hildenbrand (Arm)
2026-06-03 17:00 ` Steven Rostedt
2026-06-03 19:13 ` David Hildenbrand (Arm)
2026-06-03 19:30 ` Steven Rostedt
2026-06-03 19:31 ` Steven Rostedt [this message]
2026-06-04 1:46 ` Xie Yuanbin
2026-06-03 19:54 ` Andrew Morton
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=20260603153115.775a2e81@fedora \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=david@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=xieyuanbin1@huawei.com \
--cc=yi1.lai@intel.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