From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Nathan Chancellor <nathan@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12] lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP
Date: Mon, 21 Apr 2025 22:15:49 -0400 [thread overview]
Message-ID: <20250421194522-33bb432a057eca5d@stable.kernel.org> (raw)
In-Reply-To: <20250421153918.3248505-2-nathan@kernel.org>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: ed2b548f1017586c44f50654ef9febb42d491f31
WARNING: Author mismatch between patch and upstream commit:
Backport author: Nathan Chancellor<nathan@kernel.org>
Commit author: Kees Cook<kees@kernel.org>
Status in newer kernel trees:
6.14.y | Not found
Note: The patch differs from the upstream commit:
---
1: ed2b548f10175 < -: ------------- ubsan/overflow: Rework integer overflow sanitizer option to turn on everything
-: ------------- > 1: e3de54ebc19aa lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
next prev parent reply other threads:[~2025-04-22 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 13:55 FAILED: patch "[PATCH] lib/Kconfig.ubsan: Remove 'default UBSAN' from" failed to apply to 6.12-stable tree gregkh
2025-04-21 15:39 ` [PATCH 6.12] lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP Nathan Chancellor
2025-04-22 2:15 ` Sasha Levin [this message]
2025-04-22 7:20 ` Greg KH
2025-04-22 16:59 ` Kees Cook
2025-04-23 17:22 ` [PATCH 6.12 v2] " Nathan Chancellor
2025-04-24 13:26 ` 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=20250421194522-33bb432a057eca5d@stable.kernel.org \
--to=sashal@kernel.org \
--cc=nathan@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