From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Szymon Wilczek <swilczek.lx@gmail.com>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<syzbot+5af33dd272b913b65880@syzkaller.appspotmail.com>
Subject: Re: [PATCH] fs/ntfs3: fix deadlock in ni_readpage_cmpr
Date: Fri, 26 Dec 2025 19:06:39 +0100 [thread overview]
Message-ID: <a56398cc-22d5-41dd-9273-0e9cc17804da@paragon-software.com> (raw)
In-Reply-To: <20251222151010.17263-1-swilczek.lx@gmail.com>
On 12/22/25 16:10, Szymon Wilczek wrote:
> Syzbot reported a task hung in ni_readpage_cmpr. This is caused by a lock
> inversion deadlock involving the inode mutex (ni_lock) and page locks.
>
> Scenario:
> 1. Task A enters ntfs_read_folio() for page X. It acquires ni_lock.
> 2. Task A calls ni_readpage_cmpr(), which attempts to lock all pages in
> the compressed frame (including page Y).
> 3. Concurrently, Task B (e.g., via readahead) has locked page Y and
> calls ntfs_read_folio().
> 4. Task B waits for ni_lock (held by A).
> 5. Task A waits for page Y lock (held by B).
> -> DEADLOCK.
>
> The fix is to restructure locking: do not take ni_lock in ntfs_read_folio().
> Instead, acquire ni_lock inside ni_readpage_cmpr() ONLY AFTER all required
> page locks for the frame have been successfully acquired. This restores the
> correct lock ordering (Page Lock -> ni_lock) consistent with VFS.
>
> Reported-by: syzbot+5af33dd272b913b65880@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=5af33dd272b913b65880
> Fixes: f35590ee26f5 ("fs/ntfs3: remove ntfs_bio_pages and use page cache for compressed I/O")
> Signed-off-by: Szymon Wilczek <swilczek.lx@gmail.com>
> ---
> fs/ntfs3/frecord.c | 2 ++
> fs/ntfs3/inode.c | 3 +--
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ntfs3/frecord.c b/fs/ntfs3/frecord.c
> index 641ddaf8d4a0..f09a149cff9f 100644
> --- a/fs/ntfs3/frecord.c
> +++ b/fs/ntfs3/frecord.c
> @@ -2107,7 +2107,9 @@ int ni_readpage_cmpr(struct ntfs_inode *ni, struct folio *folio)
> pages[i] = pg;
> }
>
> + ni_lock(ni);
> err = ni_read_frame(ni, frame_vbo, pages, pages_per_frame, 0);
> + ni_unlock(ni);
>
> out1:
> for (i = 0; i < pages_per_frame; i++) {
> diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
> index 0a9ac5efeb67..33f819b162a5 100644
> --- a/fs/ntfs3/inode.c
> +++ b/fs/ntfs3/inode.c
> @@ -735,9 +735,8 @@ static int ntfs_read_folio(struct file *file, struct folio *folio)
> }
>
> if (is_compressed(ni)) {
> - ni_lock(ni);
> + /* ni_lock is taken inside ni_readpage_cmpr after page locks */
> err = ni_readpage_cmpr(ni, folio);
> - ni_unlock(ni);
> return err;
> }
>
Your patch is applied, thanks.
Regards,
Konstantin
prev parent reply other threads:[~2025-12-26 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 15:10 Szymon Wilczek
2025-12-26 18:06 ` Konstantin Komarov [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=a56398cc-22d5-41dd-9273-0e9cc17804da@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=swilczek.lx@gmail.com \
--cc=syzbot+5af33dd272b913b65880@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®