public inbox for audit@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: audit@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] audit/audit-pr-20241205
Date: Thu, 05 Dec 2024 18:06:02 -0500	[thread overview]
Message-ID: <70abed262882f79e63e747ef56a0379c@paul-moore.com> (raw)

Linus,

A minor audit patch that shuffles some code slightly to workaround a GCC
bug affecting a number of people.  The GCC folks have been able to
reproduce the problem and are discussing solutions (see the bug report
link in the commit), but since the workaround is trivial let's do that
in the kernel so we can unblock people who are hitting this.

Paul

--
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
    tags/audit-pr-20241205

for you to fetch changes up to d9381508ea2b590aff46d28d432d20bfef1ba64c:

  audit: workaround a GCC bug triggered by task comm changes
    (2024-12-04 22:57:46 -0500)

----------------------------------------------------------------
audit/stable-6.13 PR 20241205
----------------------------------------------------------------

Yafang shao (1):
      audit: workaround a GCC bug triggered by task comm changes

 kernel/auditsc.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--
paul-moore.com

             reply	other threads:[~2024-12-05 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 23:06 Paul Moore [this message]
2024-12-05 23:27 ` [GIT PULL] audit/audit-pr-20241205 pr-tracker-bot

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=70abed262882f79e63e747ef56a0379c@paul-moore.com \
    --to=paul@paul-moore.com \
    --cc=audit@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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