From: Greg KH <gregkh@linuxfoundation.org>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: sashal@kernel.org, stable@vger.kernel.org,
stable-commits@vger.kernel.org, muchun.song@linux.dev,
osalvador@suse.de, david@redhat.com
Subject: Re: Patch "hugetlbfs: skip VMAs without shareable locks in hugetlb_vmdelete_list" has been added to the 6.17-stable tree
Date: Mon, 13 Oct 2025 15:35:29 +0200 [thread overview]
Message-ID: <2025101356-take-portside-5796@gregkh> (raw)
In-Reply-To: <20251013012500.16338-1-kartikey406@gmail.com>
On Mon, Oct 13, 2025 at 06:55:00AM +0530, Deepanshu Kartikey wrote:
> Hi Sasha,
>
> Please do NOT backport commit dd83609b8898 alone to stable. This patch
> causes a regression in fallocate(PUNCH_HOLE) operations where pages are
> not freed immediately, as reported by Mark Brown.
>
> The fix for this regression is already in linux-next as commit
> 91a830422707 ("hugetlbfs: check for shareable lock before calling
> huge_pmd_unshare()").
>
> Please backport both commits together to avoid introducing the
> regression in stable kernels:
> - dd83609b88986f4add37c0871c3434310652ebd5 ("hugetlbfs: skip VMAs without shareable locks in hugetlb_vmdelete_list")
> - 91a830422707a62629fc4fbf8cdc3c8acf56ca64 ("hugetlbfs: check for shareable lock before calling huge_pmd_unshare()")
As this is not in linux-next yet, I'll just drop this original patch for
now. When it does land in Linus's tree, please let us know so we can
submit both of them to the stable queues.
thanks,
greg k-h
prev parent reply other threads:[~2025-10-13 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 1:25 Patch "hugetlbfs: skip VMAs without shareable locks in hugetlb_vmdelete_list" has been added to the 6.17-stable tree Deepanshu Kartikey
2025-10-13 13:35 ` Greg KH [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=2025101356-take-portside-5796@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=david@redhat.com \
--cc=kartikey406@gmail.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--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