From: syzbot <syzbot+251ec6887ada6eac4921@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, jmaloy@redhat.com,
jon.maloy@ericsson.com, kuba@kernel.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com,
yoshfuji@linux-ipv6.org
Subject: Re: inconsistent lock state in icmp_send
Date: Mon, 25 May 2020 03:19:04 -0700 [thread overview]
Message-ID: <000000000000f472ee05a6764e46@google.com> (raw)
In-Reply-To: <0000000000000a9cca057cd141bd@google.com>
syzbot suspects this bug was fixed by commit:
commit 1378817486d6860f6a927f573491afe65287abf1
Author: Eric Dumazet <edumazet@google.com>
Date: Thu May 21 18:29:58 2020 +0000
tipc: block BH before using dst_cache
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10cbef06100000
start commit: f5d58277 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c8970c89a0efbb23
dashboard link: https://syzkaller.appspot.com/bug?extid=251ec6887ada6eac4921
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10ab6ba3400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: tipc: block BH before using dst_cache
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-05-25 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:11 inconsistent lock state in icmp_send syzbot
2019-03-24 13:38 ` syzbot
2019-03-25 16:32 ` Jon Maloy
2020-05-25 10:19 ` syzbot [this message]
2020-11-11 14:02 ` 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=000000000000f472ee05a6764e46@google.com \
--to=syzbot+251ec6887ada6eac4921@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=jon.maloy@ericsson.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
--cc=yoshfuji@linux-ipv6.org \
/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.