From: syzbot <syzbot+96d3f9ff6a86d37e44c8@syzkaller.appspotmail.com>
To: davem@davemloft.net, kgraul@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
ubraun@linux.ibm.com
Subject: Re: WARNING: refcount bug in smc_release (2)
Date: Sun, 01 Dec 2019 04:21:01 -0800 [thread overview]
Message-ID: <000000000000ff87e40598a37ead@google.com> (raw)
In-Reply-To: <0000000000007cace40598282858@google.com>
syzbot has bisected this bug to:
commit 50717a37db032ce783f50685a73bb2ac68471a5a
Author: Ursula Braun <ubraun@linux.ibm.com>
Date: Fri Apr 12 10:57:23 2019 +0000
net/smc: nonblocking connect rework
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10a234a2e00000
start commit: 32ef9553 Merge tag 'fsnotify_for_v5.5-rc1' of git://git.ke..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=12a234a2e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14a234a2e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=ff560c3de405258c
dashboard link: https://syzkaller.appspot.com/bug?extid=96d3f9ff6a86d37e44c8
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b57336e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149e357ae00000
Reported-by: syzbot+96d3f9ff6a86d37e44c8@syzkaller.appspotmail.com
Fixes: 50717a37db03 ("net/smc: nonblocking connect rework")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-12-01 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 9:12 WARNING: refcount bug in smc_release (2) syzbot
2019-11-30 19:51 ` syzbot
2019-12-01 4:37 ` syzbot
2019-12-01 12:21 ` syzbot [this message]
[not found] <20191201122517.18720-1-hdanton@sina.com>
2019-12-04 11:47 ` Ursula Braun
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=000000000000ff87e40598a37ead@google.com \
--to=syzbot+96d3f9ff6a86d37e44c8@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=kgraul@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ubraun@linux.ibm.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).