From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzbot+c388db0347b7fc88fa7a@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] nilfs2: fix link count underflow when removing corrupted directory
Date: Tue, 06 Oct 2026 10:05:02 -0700 [thread overview]
Message-ID: <ddd05008d8007dbd56268d484d77c1e25260e6d6.camel@dubeyko.com> (raw)
In-Reply-To: <20261006090311.47123-1-konishi.ryusuke@gmail.com>
On Tue, 2026-10-06 at 17:48 +0900, Ryusuke Konishi wrote:
> When removing an empty directory with a corrupted link count (e.g.,
> i_nlink is 1 due to filesystem corruption), nilfs_rmdir() calls
> drop_nlink() via nilfs_do_unlink() and then calls drop_nlink() again
> on the directory inode. This second call causes an underflow of
> i_nlink, triggering a kernel WARNING in drop_nlink().
>
> Fix this issue by using clear_nlink() instead of drop_nlink() to
> finalize the link count reset for the target directory in
> nilfs_rmdir().
> Additionally, log a warning message when i_nlink is not 2 before
> removing an empty directory to notify about the link count
> inconsistency.
>
> Reported-by: syzbot+c388db0347b7fc88fa7a@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c388db0347b7fc88fa7a
> Fixes: d25006523d0b ("nilfs2: pathname operations")
> Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
> ---
> Hi Viacheslav,
>
> Please apply this for the next cycle.
>
> This fixes a link count underflow during rmdir on a directory with a
> corrupted link count (an issue recently reported by syzbot).
>
> Thanks,
> Ryusuke Konishi
>
> fs/nilfs2/namei.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nilfs2/namei.c b/fs/nilfs2/namei.c
> index e037e0c6e31a..d326bb1acb11 100644
> --- a/fs/nilfs2/namei.c
> +++ b/fs/nilfs2/namei.c
> @@ -341,10 +341,16 @@ static int nilfs_rmdir(struct inode *dir,
> struct dentry *dentry)
>
> err = -ENOTEMPTY;
> if (nilfs_empty_dir(inode)) {
> + if (unlikely(inode->i_nlink != 2))
> + nilfs_warn(dir->i_sb,
> + "inconsistent empty directory link
> count %u (ino=%llu)",
> + inode->i_nlink,
> + (unsigned long long)inode->i_ino);
> +
> err = nilfs_do_unlink(dir, dentry);
> if (!err) {
> inode->i_size = 0;
> - drop_nlink(inode);
> + clear_nlink(inode);
> nilfs_mark_inode_dirty(inode);
> drop_nlink(dir);
> nilfs_mark_inode_dirty(dir);
Applied.
Thanks,
Slava.
prev parent reply other threads:[~2026-10-06 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 8:48 Ryusuke Konishi
2026-10-06 17:05 ` Viacheslav Dubeyko [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=ddd05008d8007dbd56268d484d77c1e25260e6d6.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=syzbot+c388db0347b7fc88fa7a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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®