[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <000000000000ac9246059abb072c@google.com>
Date: Fri, 27 Dec 2019 19:16:01 -0800
From: syzbot <syzbot+29cc278357da941e304e@...kaller.appspotmail.com>
To: ap420073@...il.com, davem@...emloft.net, ecree@...arflare.com,
edumazet@...gle.com, jhs@...atatu.com, jiri@...lanox.com,
jiri@...nulli.us, kuznet@....inr.ac.ru,
linux-kernel@...r.kernel.org, lucien.xin@...il.com,
mcroce@...hat.com, netdev@...r.kernel.org, pabeni@...hat.com,
syzkaller-bugs@...glegroups.com, xiyou.wangcong@...il.com,
yoshfuji@...ux-ipv6.org
Subject: Re: possible deadlock in sch_direct_xmit
syzbot suspects this bug was fixed by commit:
commit 323ebb61e32b478e2432c5a3cbf9e2ca678a9609
Author: Edward Cree <ecree@...arflare.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
Powered by blists - more mailing lists