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+d27edf9f96ae85939222@syzkaller.appspotmail.com>
Subject: Re: [PATCH] ntfs3: fix circular locking dependency in run_unpack_ex
Date: Fri, 16 Jan 2026 14:40:51 +0100 [thread overview]
Message-ID: <032f7f9d-d92d-4b11-aa18-21eb62a4d2ab@paragon-software.com> (raw)
In-Reply-To: <20251227144307.8966-1-swilczek.lx@gmail.com>
On 12/27/25 15:43, Szymon Wilczek wrote:
> Syzbot reported a circular locking dependency between wnd->rw_lock
> (sbi->used.bitmap) and ni->file.run_lock.
>
> The deadlock scenario:
> 1. ntfs_extend_mft() takes ni->file.run_lock then wnd->rw_lock.
> 2. run_unpack_ex() takes wnd->rw_lock then tries to acquire
> ni->file.run_lock inside ntfs_refresh_zone().
>
> This creates an AB-BA deadlock.
>
> Fix this by using down_read_trylock() instead of down_read() when
> acquiring run_lock in run_unpack_ex(). If the lock is contended,
> skip ntfs_refresh_zone() - the MFT zone will be refreshed on the
> next MFT operation. This breaks the circular dependency since we
> never block waiting for run_lock while holding wnd->rw_lock.
>
> Reported-by: syzbot+d27edf9f96ae85939222@syzkaller.appspotmail.com
> Tested-by: syzbot+d27edf9f96ae85939222@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=d27edf9f96ae85939222
> Signed-off-by: Szymon Wilczek <swilczek.lx@gmail.com>
> ---
> fs/ntfs3/run.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/fs/ntfs3/run.c b/fs/ntfs3/run.c
> index 395b20492525..dc59cad4fa37 100644
> --- a/fs/ntfs3/run.c
> +++ b/fs/ntfs3/run.c
> @@ -1131,11 +1131,14 @@ int run_unpack_ex(struct runs_tree *run, struct ntfs_sb_info *sbi, CLST ino,
> struct rw_semaphore *lock =
> is_mounted(sbi) ? &sbi->mft.ni->file.run_lock :
> NULL;
> - if (lock)
> - down_read(lock);
> - ntfs_refresh_zone(sbi);
> - if (lock)
> - up_read(lock);
> + if (lock) {
> + if (down_read_trylock(lock)) {
> + ntfs_refresh_zone(sbi);
> + up_read(lock);
> + }
> + } else {
> + ntfs_refresh_zone(sbi);
> + }
> }
> up_write(&wnd->rw_lock);
> if (err)
Thanks for the patch. It is applied.
Regards,
Konstantin
prev parent reply other threads:[~2026-01-16 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 14:43 Szymon Wilczek
2026-01-16 13:40 ` 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=032f7f9d-d92d-4b11-aa18-21eb62a4d2ab@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+d27edf9f96ae85939222@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®