From: Steven Rostedt <rostedt@goodmis.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Yafang Shao <laoar.shao@gmail.com>,
Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Miguel Ojeda <ojeda@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
<rust-for-linux@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Justin Stitt <justinstitt@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] tracing: More updates for 6.13
Date: Fri, 29 Nov 2024 08:26:46 -0500 [thread overview]
Message-ID: <20241129082646.1341af16@rorschach.local.home> (raw)
In-Reply-To: <193780f6880.28a7.85c95baa4474aabc7814e68940a78392@paul-moore.com>
On Fri, 29 Nov 2024 08:14:56 -0500
Paul Moore <paul@paul-moore.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.
>
> I didn't pull that into the audit tree because it isn't a real patch.
> Looking at it again on my phone before today's holiday stuff kicks off, I
> don't have a problem with the workaround, but i do need to see it as a
> proper patch with a commit description, sign off, etc. before I can merge it.
Yeah, from the comment I was expecting to see a proper patch.
>
> For anyone who is going to put together a patch, please make it clear that
> it is a compiler bug and provide the associated bug report links.
If it matters, with that patch applied, all my tests were able to
complete with success.
Tested-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2024-11-29 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 18:19 [GIT PULL] tracing: More updates for 6.13 Steven Rostedt
2024-11-28 19:53 ` pr-tracker-bot
2024-11-28 19:55 ` Linus Torvalds
2024-11-28 20:51 ` Steven Rostedt
2024-11-28 23:24 ` Steven Rostedt
2024-11-29 2:16 ` Yafang Shao
2024-11-29 3:04 ` Steven Rostedt
2024-11-29 13:14 ` Paul Moore
2024-11-29 13:26 ` Steven Rostedt [this message]
2024-11-29 23:08 ` Paul Moore
2024-11-29 9:36 ` Alice Ryhl
-- strict thread matches above, loose matches on Subject: below --
2024-11-27 16:34 Steven Rostedt
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=20241129082646.1341af16@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=bigeasy@linutronix.de \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox