All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Roman Kisel <romank@linux.microsoft.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Kees Cook <kees@kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: Patch "coredump: Standartize and fix logging" has been added to the 6.10-stable tree
Date: Mon, 7 Oct 2024 14:45:51 -0400	[thread overview]
Message-ID: <ZwQsX9pMUXKEOlsj@sashalap> (raw)
In-Reply-To: <6144d8b5-8b3d-42d9-bf28-b88327f29124@linux.microsoft.com>

On Mon, Oct 07, 2024 at 10:36:56AM -0700, Roman Kisel wrote:
>Adding also Oleg as it was my impression from working with Oleg,
>this area might be of interest for Oleg. I've crossed paths with
>very few people who contribute to the "./kernel", and don't know
>who to ask for another look if this is safe for the stable kernel.
>
>Let us err on the side of caution perhaps unless folks are sure
>all is going to be well with the stable kernel and get_task_comm().
>Another datapoint would be that Linus reverted this change from
>6.12-rc1.

Let's play it safe and drop them. Thanks for the report!

-- 
Thanks,
Sasha

      reply	other threads:[~2024-10-07 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241006152737.10366-1-sashal@kernel.org>
2024-10-07 17:26 ` Patch "coredump: Standartize and fix logging" has been added to the 6.10-stable tree Roman Kisel
2024-10-07 17:36   ` Roman Kisel
2024-10-07 18:45     ` Sasha Levin [this message]

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=ZwQsX9pMUXKEOlsj@sashalap \
    --to=sashal@kernel.org \
    --cc=brauner@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=jack@suse.cz \
    --cc=kees@kernel.org \
    --cc=oleg@redhat.com \
    --cc=romank@linux.microsoft.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.