From: syzbot <syzbot+29cc278357da941e304e@syzkaller.appspotmail.com>
To: ap420073@gmail.com, davem@davemloft.net, ecree@solarflare.com,
edumazet@google.com, jhs@mojatatu.com, jiri@mellanox.com,
jiri@resnulli.us, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, lucien.xin@gmail.com,
mcroce@redhat.com, netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, xiyou.wangcong@gmail.com,
yoshfuji@linux-ipv6.org
Subject: Re: possible deadlock in sch_direct_xmit
Date: Fri, 27 Dec 2019 19:16:01 -0800 [thread overview]
Message-ID: <000000000000ac9246059abb072c@google.com> (raw)
In-Reply-To: <089e0825d4a4d2cb2a0562e878f1@google.com>
syzbot suspects this bug was fixed by commit:
commit 323ebb61e32b478e2432c5a3cbf9e2ca678a9609
Author: Edward Cree <ecree@solarflare.com>
Date: Tue Aug 6 13:53:55 2019 +0000
net: use listified RX for handling GRO_NORMAL skbs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14647ab9e00000
start commit: c92a9a46
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=46986c099cb53bc6
dashboard link: https://syzkaller.appspot.com/bug?extid=29cc278357da941e304e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143636c9800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16856849800000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: net: use listified RX for handling GRO_NORMAL skbs
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-12-28 3:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 17:58 possible deadlock in sch_direct_xmit syzbot
2019-11-30 21:04 ` syzbot
2019-12-28 3:16 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-06 9:27 Hao Sun
2022-08-29 6:55 Jiacheng Xu
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=000000000000ac9246059abb072c@google.com \
--to=syzbot+29cc278357da941e304e@syzkaller.appspotmail.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.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.