From: Sasha Levin <sashal@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Kees Cook <kees@kernel.org>,
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 19:32:47 -0400 [thread overview]
Message-ID: <aA1tH4vcHu4jzqnc@lappy> (raw)
In-Reply-To: <20250426151248.GA2377568@ax162>
On Sat, Apr 26, 2025 at 11:12:48AM -0400, Nathan Chancellor wrote:
>On Sat, Apr 26, 2025 at 10:52:32AM -0400, Sasha Levin wrote:
>> On Sat, Apr 26, 2025 at 10:11:07AM -0400, Nathan Chancellor wrote:
>> > 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
>>
>> Appologies: this is a case where some things falls through the cracks
>> between Greg and myself. Let me explain...
>>
>> Greg is usually picking up patches from the mailing list. I have the
>> annoying bot (which you might have seen) that tests backports folks send
>> over, but in reality I would rarely apply a backport someone sent over
>> (even if only so we won't step on each other's toes).
>>
>> On the other hand, I have some automation in place that after a few
>> days, it combs through the FAILED: mails that Greg sends out and will
>> attempt to automatically resolve conflicts by bringing in dependencies
>> and build testing the code.
>
>Maybe that automation could look to see if a patch has already been sent
>to the FAILED thread? Greg's instructions tell people to use
>'--in-reply-to' with the FAILED message ID so it would probably cover
>the vast majority of cases of manually backport.
Yeah, it could be improved like you've suggested.
One of the reasons I'm not tackling it yet is because it's a bit "old"
and I need to rework it to use the lore/lei infra we now have and I'm a
bit overloaded to try and tackle that.
I think that ignoring any "FAILED:" mails that have any replies makes
sense here.
>> I promise I haven't "manually" ignored your backports :)
>
>Sorry, I did not mean for that to sound as harsh and accusatory as it
>was and I appreciate the additional clarification around the process so
>that it can potentially be improved :) thanks for all the work you and
>Greg do.
No worries, thanks for the backports! :)
--
Thanks,
Sasha
prev parent reply other threads:[~2025-04-26 23:32 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
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 [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=aA1tH4vcHu4jzqnc@lappy \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=elver@google.com \
--cc=kees@kernel.org \
--cc=nathan@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--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