From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
syzbot+16bf7cd0ebeb1de93aa5@syzkaller.appspotmail.com,
Lance Yang <lance.yang@linux.dev>,
Pedro Falcato <pfalcato@suse.de>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [PATCH 6.12.y] khugepaged: fix readahead lock inversion in collapse_file()
Date: Thu, 12 Nov 2026 21:33:17 -0500 [thread overview]
Message-ID: <daily-reply-2026-11-12-6442443928@kernel.org> (raw)
In-Reply-To: <20261111132605.88959-1-lance.yang@linux.dev>
On 2026-11-11, Lance Yang wrote:
> [PATCH 6.12.y] khugepaged: fix readahead lock inversion in collapse_file()
> collapse_file() can call page_cache_sync_readahead() while still holding
> source folios locked. If truncate holds mapping->invalidate_lock
> exclusively and waits for one of those folios, readahead waits for
The 6.18 and 6.12 backports replace filemap_invalidate_lock_shared() with a
trylock plus rollback, which mainline doesn't have, and the
reviewed-by/acked-by tags from eadce52a9ef6 ("khugepaged: fix readahead lock
inversion in collapse_file()") only cover the mainline patch.
David, Zi: could you ack this change?
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-13 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 1:09 FAILED: patch "[PATCH] khugepaged: fix readahead lock inversion in collapse_file()" failed to apply to 6.12-stable tree Sasha Levin
2026-11-11 13:26 ` [PATCH 6.12.y] khugepaged: fix readahead lock inversion in collapse_file() Lance Yang
2026-11-13 2:33 ` 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=daily-reply-2026-11-12-6442443928@kernel.org \
--to=sashal@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=lance.yang@linux.dev \
--cc=pfalcato@suse.de \
--cc=stable@vger.kernel.org \
--cc=syzbot+16bf7cd0ebeb1de93aa5@syzkaller.appspotmail.com \
--cc=ziy@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.