public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: 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>,
	Paul Moore <paul@paul-moore.com>,
	Justin Stitt <justinstitt@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kees Cook <keescook@chromium.org>
Subject: Re: [GIT PULL] tracing: More updates for 6.13
Date: Thu, 28 Nov 2024 22:04:20 -0500	[thread overview]
Message-ID: <20241128220420.6196a937@rorschach.local.home> (raw)
In-Reply-To: <CALOAHbBB-__eyERw82QnS3Wmgi7_BpPaacY2urVmpWX3ZkVtvQ@mail.gmail.com>

On Fri, 29 Nov 2024 10:16:54 +0800
Yafang Shao <laoar.shao@gmail.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

  reply	other threads:[~2024-11-29  3:04 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 [this message]
2024-11-29 13:14         ` Paul Moore
2024-11-29 13:26           ` Steven Rostedt
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=20241128220420.6196a937@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