From: Dominique Martinet <asmadeus@codewreck.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.12.99
Date: Mon, 10 Aug 2026 12:50:46 +0900 [thread overview]
Message-ID: <anlKlnYz1on6qET_@codewreck.org> (raw)
In-Reply-To: <2026072931-buddhist-lethargy-769b@gregkh>
Greg Kroah-Hartman wrote on Wed, Jul 29, 2026 at 06:17:30PM +0200:
> Lorenzo Stoakes (1):
> mm: refactor mm_access() to not return NULL
FWIW if anyone else cares and looks for this, this backport was required
due to a NULL deref in 6.12.98 (and likely .97 as well if commit
4bfe8c481846 ("proc: protect ptrace_may_access() with exec_update_lock
(part 1)") is indeed the culprit, I didn't check):
https://lore.kernel.org/all/2026072933-widow-grouped-f9e4@gregkh/T/#u
Greg & Sasha,
this is purely selfish and I'm grateful for all the work you two do
backporting patches, but (for next times) it'd be great if the backport
commit could also point at why it is backported after all this time
(for example add a comment or even just the above link between the
original sign-off and your's) -- it doesn't have to be much, but it took
me a while to find (I was curious because this was an urgent release
without -rc, with a single 2 year old patch branded as refactor not
fixing anything obvious...)
Ultimately it doesn't change the fact that "all users must upgrade" as
said in the announce, but I need to judge the urgency of the upgrade, so
having a rationale is extremely useful.
If backported commits fix something obvious then there's nothing to add,
but in this case I believe I'm not the only one who'd puzzle over it (if
someone is actually looking...)
Thanks!
--
Dominique Martinet
next prev parent reply other threads:[~2026-08-10 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 16:17 Linux 6.12.99 Greg Kroah-Hartman
2026-07-29 16:17 ` Greg Kroah-Hartman
2026-08-10 3:50 ` Dominique Martinet [this message]
2026-08-10 13:32 ` David Niklas
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=anlKlnYz1on6qET_@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=sashal@kernel.org \
--cc=stable@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