From: syzbot <syzbot+61ffbb75d30176841f76@syzkaller.appspotmail.com>
To: arvid.brodin@alten.se, bristot@redhat.com, davem@davemloft.net,
kuba@kernel.org, linux-kernel@vger.kernel.org, mingo@kernel.org,
netdev@vger.kernel.org, peterz@infradead.org,
simon.horman@netronome.com, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com
Subject: Re: possible deadlock in __static_key_slow_dec
Date: Sun, 08 Mar 2020 20:09:02 -0700 [thread overview]
Message-ID: <0000000000003a9d4f05a063536a@google.com> (raw)
In-Reply-To: <0000000000006f20e205a01ef5e1@google.com>
syzbot has bisected this bug to:
commit b9a1e627405d68d475a3c1f35e685ccfb5bbe668
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Thu Jul 4 00:21:13 2019 +0000
hsr: implement dellink to clean up resources
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1449a0b1e00000
start commit: 63623fd4 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1649a0b1e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1249a0b1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d2e033af114153f
dashboard link: https://syzkaller.appspot.com/bug?extid=61ffbb75d30176841f76
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f0efa1e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119cf3b5e00000
Reported-by: syzbot+61ffbb75d30176841f76@syzkaller.appspotmail.com
Fixes: b9a1e627405d ("hsr: implement dellink to clean up resources")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-03-09 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 17:35 possible deadlock in __static_key_slow_dec syzbot
2020-03-05 20:24 ` Peter Zijlstra
2020-03-09 3:09 ` syzbot [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=0000000000003a9d4f05a063536a@google.com \
--to=syzbot+61ffbb75d30176841f76@syzkaller.appspotmail.com \
--cc=arvid.brodin@alten.se \
--cc=bristot@redhat.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=simon.horman@netronome.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.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 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.