From: syzbot <syzbot+90d5ec0c05e708f3b66d@syzkaller.appspotmail.com>
To: ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, dsahern@gmail.com, johannes.berg@intel.com,
kafai@fb.com, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, posk@google.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
willemb@google.com, yhs@fb.com, yoshfuji@linux-ipv6.org
Subject: Re: kernel BUG at net/ipv4/ip_output.c:LINE!
Date: Thu, 07 Nov 2019 05:42:08 -0800 [thread overview]
Message-ID: <000000000000e51d450596c1d472@google.com> (raw)
In-Reply-To: <000000000000f68d660570dcddd8@google.com>
syzbot suspects this bug was fixed by commit:
commit e7c87bd6cc4ec7b0ac1ed0a88a58f8206c577488
Author: Willem de Bruijn <willemb@google.com>
Date: Wed Jan 16 01:19:22 2019 +0000
bpf: in __bpf_redirect_no_mac pull mac only if present
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14175486600000
start commit: 112cbae2 Merge branch 'linus' of git://git.kernel.org/pub/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=152cb8ccd35b1f70
dashboard link: https://syzkaller.appspot.com/bug?extid=90d5ec0c05e708f3b66d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=153ed6e2400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1539038c400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: bpf: in __bpf_redirect_no_mac pull mac only if present
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-07 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 8:00 kernel BUG at net/ipv4/ip_output.c:LINE! syzbot
2018-07-29 11:12 ` syzbot
2018-08-09 20:02 ` syzbot
2019-11-07 13:42 ` syzbot [this message]
2019-11-07 16:58 ` 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=000000000000e51d450596c1d472@google.com \
--to=syzbot+90d5ec0c05e708f3b66d@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kafai@fb.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=posk@google.com \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=willemb@google.com \
--cc=yhs@fb.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.