[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241128220420.6196a937@rorschach.local.home>
Date: Thu, 28 Nov 2024 22:04:20 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Yafang Shao <laoar.shao@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Masami Hiramatsu
<mhiramat@...nel.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Thomas Gleixner <tglx@...utronix.de>, Sebastian Andrzej Siewior
<bigeasy@...utronix.de>, Miguel Ojeda <ojeda@...nel.org>, Alice Ryhl
<aliceryhl@...gle.com>, rust-for-linux@...r.kernel.org, LKML
<linux-kernel@...r.kernel.org>, Paul Moore <paul@...l-moore.com>, Justin
Stitt <justinstitt@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>
Subject: Re: [GIT PULL] tracing: More updates for 6.13
On Fri, 29 Nov 2024 10:16:54 +0800
Yafang Shao <laoar.shao@...il.com> wrote:
> The issue appears to be a known GCC bug, though the root cause remains
> unclear at this time.
>
> A potential workaround has been proposed, which you can find here:
> https://lore.kernel.org/linux-hardening/202410171059.C2C395030@keescook/
>
> However, it seems that the patch has not yet been accepted into the mainline.
Thanks, I applied that to my "fixes" patch that is used to fix other
issues that are not related to my code so that I can continue testing.
I just kicked off my tests again with that applied.
-- Steve
Powered by blists - more mailing lists