All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1c8034b9f0e640f9ba45@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	miklos@szeredi.hu, mszeredi@redhat.com,
	syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] WARNING in inc_nlink (2)
Date: Tue, 16 Nov 2021 21:32:09 -0800	[thread overview]
Message-ID: <00000000000006b5b205d0f55d49@google.com> (raw)
In-Reply-To: <000000000000c93bd505bf3646ed@google.com>

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:

#syz fix: fuse: don't increment nlink in link()

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2021-11-17  5:32 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 [this message]
2021-11-17  7:25   ` Miklos Szeredi
2021-11-25 11:23     ` Dmitry Vyukov

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=00000000000006b5b205d0f55d49@google.com \
    --to=syzbot+1c8034b9f0e640f9ba45@syzkaller.appspotmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.