From: syzbot <syzbot+3f1fd6b8cbf8702d134e@syzkaller.appspotmail.com>
To: davem@davemloft.net, dhowells@redhat.com, kuba@kernel.org,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: inconsistent lock state in rxrpc_put_client_conn
Date: Mon, 03 Feb 2020 21:41:01 -0800 [thread overview]
Message-ID: <00000000000034bde7059db97cf4@google.com> (raw)
In-Reply-To: <000000000000350337059db54167@google.com>
syzbot has bisected this bug to:
commit 5273a191dca65a675dc0bcf3909e59c6933e2831
Author: David Howells <dhowells@redhat.com>
Date: Thu Jan 30 21:50:36 2020 +0000
rxrpc: Fix NULL pointer deref due to call->conn being cleared on disconnect
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1182314ee00000
start commit: 3d80c653 Merge tag 'rxrpc-fixes-20200203' of git://git.ker..
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=1382314ee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1582314ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=95b275782b150c86
dashboard link: https://syzkaller.appspot.com/bug?extid=3f1fd6b8cbf8702d134e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ac314ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ec4c5ee00000
Reported-by: syzbot+3f1fd6b8cbf8702d134e@syzkaller.appspotmail.com
Fixes: 5273a191dca6 ("rxrpc: Fix NULL pointer deref due to call->conn being cleared on disconnect")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-02-04 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 0:38 inconsistent lock state in rxrpc_put_client_conn syzbot
2020-02-04 5:41 ` syzbot [this message]
[not found] <20200207031553.18696-1-hdanton@sina.com>
[not found] ` <20200204084005.11320-1-hdanton@sina.com>
2020-02-06 13:09 ` David Howells
2020-02-07 7:23 ` David Howells
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=00000000000034bde7059db97cf4@google.com \
--to=syzbot+3f1fd6b8cbf8702d134e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).