From: syzbot <syzbot+29cc278357da941e304e@syzkaller.appspotmail.com>
To: davem@davemloft.net, jhs@mojatatu.com, jiri@resnulli.us,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
lucien.xin@gmail.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: Sat, 30 Nov 2019 13:04:01 -0800 [thread overview]
Message-ID: <0000000000008e8a99059896af4c@google.com> (raw)
In-Reply-To: <089e0825d4a4d2cb2a0562e878f1@google.com>
syzbot has bisected this bug to:
commit c84bed440e4e11a973e8c0254d0dfaccfca41fb0
Author: Xin Long <lucien.xin@gmail.com>
Date: Sun Oct 1 14:00:56 2017 +0000
ip_gre: erspan device should keep dst
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=153a767ee00000
start commit: c92a9a46
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=173a767ee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=133a767ee00000
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
Reported-by: syzbot+29cc278357da941e304e@syzkaller.appspotmail.com
Fixes: c84bed440e4e ("ip_gre: erspan device should keep dst")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-30 21:04 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 [this message]
2019-12-28 3:16 ` syzbot
-- 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=0000000000008e8a99059896af4c@google.com \
--to=syzbot+29cc278357da941e304e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.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.