From: syzbot <syzbot+2b713236b28823cd4dff@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, jmaloy@redhat.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: WARNING: locking bug in try_to_grab_pending
Date: Fri, 14 Aug 2020 06:17:07 -0700 [thread overview]
Message-ID: <000000000000dbe6ee05acd63ca2@google.com> (raw)
In-Reply-To: <0000000000006dc0290581ca413e@google.com>
syzbot suspects this issue 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=175599f6900000
start commit: 6663cf82 flow_offload: Fix flow action infrastructure
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=8572a6e4661225f4
dashboard link: https://syzkaller.appspot.com/bug?extid=2b713236b28823cd4dff
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13e932a8c00000
If the result looks correct, please mark the issue as 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-08-14 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 17:56 WARNING: locking bug in try_to_grab_pending syzbot
2020-08-14 13:17 ` syzbot [this message]
2020-08-14 15:05 ` Eric Dumazet
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=000000000000dbe6ee05acd63ca2@google.com \
--to=syzbot+2b713236b28823cd4dff@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.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 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).