Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Kees Cook <kees@kernel.org>, Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Marco Elver <elver@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Patch "lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP" has been added to the 6.14-stable tree
Date: Sat, 26 Apr 2025 10:11:07 -0400	[thread overview]
Message-ID: <20250426141107.GA3689756@ax162> (raw)
In-Reply-To: <71399E4C-AAD6-4ACF-8256-8866394F3895@kernel.org>

On Sat, Apr 26, 2025 at 06:33:24AM -0700, Kees Cook wrote:
> 
> 
> On April 26, 2025 6:25:09 AM PDT, Sasha Levin <sashal@kernel.org> wrote:
> >This is a note to let you know that I've just added the patch titled
> >
> >    lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP
> >
> >to the 6.14-stable tree which can be found at:
> >    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> >The filename of the patch is:
> >     lib-kconfig.ubsan-remove-default-ubsan-from-ubsan_in.patch
> >and it can be found in the queue-6.14 subdirectory.
> >
> >If you, or anyone else, feels it should not be added to the stable tree,
> >please let <stable@vger.kernel.org> know about it.
> 
> Please drop this; it's fixing the other patch that should not be backported. :)

This one is still technically needed but I already sent a manual
backport for this...

https://lore.kernel.org/stable/20250423172241.1135309-2-nathan@kernel.org/
https://lore.kernel.org/stable/20250423172504.1334237-2-nathan@kernel.org/

Sasha, it is a little insulting to me to have my manual backports
ignored while you pull in extra unnecessary changes to make them apply
cleanly, especially since I sent them straight to you. I already spent
the effort to account for the conflict, which was not big or nasty
enough to justify pulling in the upstream solution, especially when it
is still not ready for prime time, hence this change...

Cheers,
Nathan

  reply	other threads:[~2025-04-26 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250426132510.808646-1-sashal@kernel.org>
2025-04-26 13:33 ` Patch "lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP" has been added to the 6.14-stable tree Kees Cook
2025-04-26 14:11   ` Nathan Chancellor [this message]
2025-04-26 14:30     ` Kees Cook
2025-04-26 14:52     ` Sasha Levin
2025-04-26 15:12       ` Nathan Chancellor
2025-04-26 23:32         ` Sasha Levin

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=20250426141107.GA3689756@ax162 \
    --to=nathan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=elver@google.com \
    --cc=kees@kernel.org \
    --cc=ryabinin.a.a@gmail.com \
    --cc=sashal@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.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