From: syzbot <syzbot+228a82b263b5da91883d@syzkaller.appspotmail.com>
To: anna.schumaker@netapp.com, bcodding@redhat.com,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
rbergant@redhat.com, syzkaller-bugs@googlegroups.com,
trond.myklebust@hammerspace.com
Subject: Re: WARNING: locking bug in nfs_get_client
Date: Wed, 08 May 2019 19:46:00 -0700 [thread overview]
Message-ID: <0000000000004dd97205886b7337@google.com> (raw)
In-Reply-To: <000000000000c3e9dc0588695e22@google.com>
syzbot has bisected this bug to:
commit 950a578c6128c2886e295b9c7ecb0b6b22fcc92b
Author: Roberto Bergantinos Corpas <rbergant@redhat.com>
Date: Thu Apr 25 13:36:51 2019 +0000
NFS: make nfs_match_client killable
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11e40aaca00000
start commit: 31ccad9b Add linux-next specific files for 20190508
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=13e40aaca00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15e40aaca00000
kernel config: https://syzkaller.appspot.com/x/.config?x=63cd766601c6c9fc
dashboard link: https://syzkaller.appspot.com/bug?extid=228a82b263b5da91883d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=140fdce8a00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=134dce02a00000
Reported-by: syzbot+228a82b263b5da91883d@syzkaller.appspotmail.com
Fixes: 950a578c6128 ("NFS: make nfs_match_client killable")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-05-09 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 0:17 WARNING: locking bug in nfs_get_client syzbot
2019-05-09 2:46 ` syzbot [this message]
2019-05-09 10:55 ` Benjamin Coddington
2019-05-09 11:37 ` Benjamin Coddington
2019-05-09 12:06 ` Schumaker, Anna
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=0000000000004dd97205886b7337@google.com \
--to=syzbot+228a82b263b5da91883d@syzkaller.appspotmail.com \
--cc=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rbergant@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trond.myklebust@hammerspace.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;
as well as URLs for NNTP newsgroup(s).