From: "Zhou, Yun" <yun.zhou@windriver.com>
To: Christian Aurich Zanettini Martins <christian.aurichzm@gmail.com>,
almaz.alexandrovich@paragon-software.com
Cc: ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org,
syzbot+5c0ed4f2974a8b100ed4@syzkaller.appspotmail.com
Subject: Re: [PATCH] fs/ntfs3: fix double ni_unlock() in ntfs_readdir()
Date: Thu, 29 Oct 2026 11:25:26 +0800 [thread overview]
Message-ID: <eeaabd5c-7df2-41fa-8f43-69c8d4853e7c@windriver.com> (raw)
In-Reply-To: <20261023223533.686085-1-christian.aurichzm@gmail.com>
On 10/24/26 06:35, Christian Aurich Zanettini Martins wrote:
> Commit da4391c496fe ("ntfs3: release ni_lock before dir_emit in
> ntfs_readdir to fix deadlocks") drops ni_lock before calling
> ntfs_read_hdr() in ntfs_readdir(). If either call returns non-zero,
> execution jumps to out, which calls ni_unlock() even though the lock
> is no longer held.
>
The issue does indeed exist in the current linux-next (next-20261027),
but it was not introduced by da4391c496. When da4391c496 was committed
on July 1, fb058ccff57 had not yet been applied; fb058ccff57 was only
applied on October 8. This patch made the following changes (directly
altering the position of the out label):
-out_unlock:
+out:
ni_unlock(ni);
-out:
kfree(name);
put_indx_node(node);
The issue is caused by a conflict between two patches from different
time periods.
> This also happens when getdents64() fills the supplied buffer,
> triggering a lockdep "bad unlock balance" warning.
>
> Jump to out_free instead to avoid unlocking an already released lock.
>
> Reported-by: syzbot+5c0ed4f2974a8b100ed4@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=5c0ed4f2974a8b100ed4
> Fixes: da4391c496fe ("ntfs3: release ni_lock before dir_emit in ntfs_readdir to fix deadlocks")
> Signed-off-by: Christian Aurich Zanettini Martins <christian.aurichzm@gmail.com>
> ---
> Based on Paragon's ntfs3 master (da4391c496fe), also in linux-next.
>
> Tested in QEMU with lockdep. A 128-byte getdents64() buffer
> reproduced the warning before the fix. After the fix, no warning
> occurred when reading root-only and 700-entry directories,
> including four concurrent readers and a writer.
>
> fs/ntfs3/dir.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ntfs3/dir.c b/fs/ntfs3/dir.c
> index b54828735d55..45d6a41a7222 100644
> --- a/fs/ntfs3/dir.c
> +++ b/fs/ntfs3/dir.c
> @@ -563,7 +563,7 @@ static int ntfs_readdir(struct file *file, struct dir_context *ctx)
> */
> err = ntfs_read_hdr(sbi, ni, &root->ihdr, 0, pos, name, ctx);
> if (err)
> - goto out;
> + goto out_free;
>
> ni_lock(ni);
> bit = 0;
> @@ -607,7 +607,7 @@ static int ntfs_readdir(struct file *file, struct dir_context *ctx)
> ((u64)bit << index_bits) + sbi->record_size,
> pos, name, ctx);
> if (err)
> - goto out;
> + goto out_free;
>
> ni_lock(ni);
> }
> @@ -615,6 +615,7 @@ static int ntfs_readdir(struct file *file, struct dir_context *ctx)
> out:
> ni_unlock(ni);
>
> +out_free:
> kfree(name);
> put_indx_node(node);
>
> base-commit: da4391c496fedc1ca78a99907712f2256ce8fb80
next prev parent reply other threads:[~2026-10-29 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 22:35 Christian Aurich Zanettini Martins
2026-10-29 3:25 ` Zhou, Yun [this message]
2026-10-29 5:17 ` Christian Aurich Zanettini Martins
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=eeaabd5c-7df2-41fa-8f43-69c8d4853e7c@windriver.com \
--to=yun.zhou@windriver.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=christian.aurichzm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+5c0ed4f2974a8b100ed4@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®