From: Dmitry Vyukov <dvyukov@google.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: syzbot <syzbot+1c8034b9f0e640f9ba45@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Miklos Szeredi <mszeredi@redhat.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [syzbot] WARNING in inc_nlink (2)
Date: Thu, 25 Nov 2021 12:23:02 +0100 [thread overview]
Message-ID: <CACT4Y+bJ4Ap74hBOBg7WMNDvhkjE2soD4MZ267gGP11G6s7Dsw@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegtASmSmbNakuCYcgaF0Cy8kY=wu-w9_imiJnsCJngnR=A@mail.gmail.com>
On Wed, 17 Nov 2021 at 08:25, Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Wed, 17 Nov 2021 at 06:32, syzbot
> <syzbot+1c8034b9f0e640f9ba45@syzkaller.appspotmail.com> wrote:
> >
> > syzbot suspects this issue was fixed by commit:
> >
> > commit 97f044f690bac2b094bfb7fb2d177ef946c85880
> > Author: Miklos Szeredi <mszeredi@redhat.com>
> > Date: Fri Oct 22 15:03:02 2021 +0000
> >
> > fuse: don't increment nlink in link()
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10563ac9b00000
> > start commit: 1da38549dd64 Merge tag 'nfsd-5.15-3' of git://git.kernel.o..
> > git tree: upstream
> > kernel config: https://syzkaller.appspot.com/x/.config?x=e2ffb281e6323643
> > dashboard link: https://syzkaller.appspot.com/bug?extid=1c8034b9f0e640f9ba45
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f16d57300000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15758d57300000
> >
> > If the result looks correct, please mark the issue as fixed by replying with:
>
> Highly unlikely: the original report was for sysvfs and the fix is for fuse.
Hi Miklos,
The fuse bug was folded into this report (on the dashboard you can see
examples of reports in fuse).
This is unavoidable for bugs that are left unaddressed for long. They
become piles of assorted stuff.
Now the best course of action is to mark it as fixed. Or we will
exacerbate the problem even more: it will be a bug about sysvfs, this
fuse bug, and the next similar bug in fuse and bugs in other file
systems.
#syz fix: fuse: don't increment nlink in link()
prev parent reply other threads:[~2021-11-25 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 9:25 [syzbot] WARNING in inc_nlink (2) syzbot
2021-11-17 5:32 ` syzbot
2021-11-17 7:25 ` Miklos Szeredi
2021-11-25 11:23 ` Dmitry Vyukov [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=CACT4Y+bJ4Ap74hBOBg7WMNDvhkjE2soD4MZ267gGP11G6s7Dsw@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=syzbot+1c8034b9f0e640f9ba45@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).