From: Sasha Levin <sashal@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, linux-mm@kvack.org,
Oleg Nesterov <oleg@redhat.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 6.12.y] kernel: be more careful about dup_mmap() failures and uprobe registering
Date: Mon, 20 Apr 2026 09:21:09 -0400 [thread overview]
Message-ID: <20260420-stable-reply-dup-mmap-uprobe-6-12@kernel.org> (raw)
In-Reply-To: <20260415180623.199818-1-heiko@sntech.de>
On Wed, Apr 15, 2026, Heiko Stuebner wrote:
> Backport of 64c37e134b12 ("kernel: be more careful about dup_mmap()
> failures and uprobe registering") to 6.12.y.
Queued for 6.12, thanks.
--
Thanks,
Sasha
parent reply other threads:[~2026-04-20 13:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260415180623.199818-1-heiko@sntech.de>]
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=20260420-stable-reply-dup-mmap-uprobe-6-12@kernel.org \
--to=sashal@kernel.org \
--cc=heiko@sntech.de \
--cc=jack@suse.cz \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--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