From: syzbot <syzbot+2e37f794f31be5667a88@syzkaller.appspotmail.com>
To: allison@lohutok.net, andy.shevchenko@gmail.com,
davem@davemloft.net, douly.fnst@cn.fujitsu.com,
gregkh@linuxfoundation.org, hpa@zytor.com, info@metux.net,
jbenc@redhat.com, jgross@suse.com, kstewart@linuxfoundation.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, ville.syrjala@linux.intel.com,
willemb@google.com, x86@kernel.org
Subject: Re: general protection fault in propagate_entity_cfs_rq
Date: Thu, 07 Nov 2019 05:42:09 -0800 [thread overview]
Message-ID: <000000000000f5a6620596c1d43e@google.com> (raw)
In-Reply-To: <0000000000008c6be40570d8a9d8@google.com>
syzbot suspects this bug was fixed by commit:
commit bab2c80e5a6c855657482eac9e97f5f3eedb509a
Author: Willem de Bruijn <willemb@google.com>
Date: Wed Jul 11 16:00:44 2018 +0000
nsh: set mac len based on inner packet
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=170cc89c600000
start commit: 6fd06660 Merge branch 'bpf-arm-jit-improvements'
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=a501a01deaf0fe9
dashboard link: https://syzkaller.appspot.com/bug?extid=2e37f794f31be5667a88
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1014db94400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11f81e78400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: nsh: set mac len based on inner packet
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2019-11-07 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000008c6be40570d8a9d8@google.com>
2019-11-07 13:42 ` syzbot [this message]
2019-11-07 14:58 ` general protection fault in propagate_entity_cfs_rq Willem de Bruijn
2019-11-07 15:16 ` Willem de Bruijn
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=000000000000f5a6620596c1d43e@google.com \
--to=syzbot+2e37f794f31be5667a88@syzkaller.appspotmail.com \
--cc=allison@lohutok.net \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=douly.fnst@cn.fujitsu.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=info@metux.net \
--cc=jbenc@redhat.com \
--cc=jgross@suse.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=ville.syrjala@linux.intel.com \
--cc=willemb@google.com \
--cc=x86@kernel.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).