From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<syzbot+5f6ca38579a76e303c1c@syzkaller.appspotmail.com>
Subject: Re: [PATCH] ntfs3: fix deadlock in ntfs_force_shutdown
Date: Wed, 15 Apr 2026 17:50:45 +0200 [thread overview]
Message-ID: <1cb0dc3a-dadd-4df3-9ccf-88070a8959e7@paragon-software.com> (raw)
In-Reply-To: <20260404153213.365836-1-kartikey406@gmail.com>
On 4/4/26 17:32, Deepanshu Kartikey wrote:
> ntfs_force_shutdown() calls bdev_freeze() which internally calls
> freeze_super(). freeze_super() calls sb_wait_write() which waits
> for all active sb_writers holders to finish.
>
> However active writers (ntfs_compress_write) can be stuck waiting
> for ni->file.run_lock while holding the sb_writers read lock
> acquired via file_start_write() in the VFS layer. This creates
> a deadlock where freeze_super() waits for writers that can never
> complete because they are blocked on run_lock contention.
>
> Fix by removing bdev_freeze/bdev_thaw entirely. The shutdown bit
> NTFS_FLAGS_SHUTDOWN_BIT is already checked at entry of all ntfs3
> write paths (file.c, inode.c, namei.c, frecord.c, fsntfs.c,
> super.c, xattr.c) and causes them to return errors immediately,
> making further writes impossible without risking a deadlock.
>
> Reported-by: syzbot+5f6ca38579a76e303c1c@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=5f6ca38579a76e303c1c
> Tested-by: syzbot+5f6ca38579a76e303c1c@syzkaller.appspotmail.com
> Fixes: ae91dfe38966 ("fs/ntfs3: implement NTFS3_IOC_SHUTDOWN ioctl")
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
> ---
> fs/ntfs3/file.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/fs/ntfs3/file.c b/fs/ntfs3/file.c
> index 7eecf1e01f74..cbbc7d81875f 100644
> --- a/fs/ntfs3/file.c
> +++ b/fs/ntfs3/file.c
> @@ -118,18 +118,12 @@ static int ntfs_ioctl_set_volume_label(struct ntfs_sb_info *sbi, u8 __user *buf)
> */
> static int ntfs_force_shutdown(struct super_block *sb, u32 flags)
> {
> - int err;
> struct ntfs_sb_info *sbi = sb->s_fs_info;
>
> if (unlikely(ntfs3_forced_shutdown(sb)))
> return 0;
>
> - /* No additional options yet (flags). */
> - err = bdev_freeze(sb->s_bdev);
> - if (err)
> - return err;
> set_bit(NTFS_FLAGS_SHUTDOWN_BIT, &sbi->flags);
> - bdev_thaw(sb->s_bdev);
> return 0;
> }
>
Hello,
Your patch is applied. Thank you.
Regards,
Konstantin
next prev parent reply other threads:[~2026-04-15 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 15:32 Deepanshu Kartikey
2026-04-11 5:23 ` Deepanshu Kartikey
2026-04-15 15:50 ` Konstantin Komarov [this message]
2026-04-16 8:39 ` Konstantin Komarov
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=1cb0dc3a-dadd-4df3-9ccf-88070a8959e7@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+5f6ca38579a76e303c1c@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®