From: syzbot <syzbot+554266c04a41d1f9754d@syzkaller.appspotmail.com>
To: alan.brady@intel.com, andrewx.bowers@intel.com,
davem@davemloft.net, ebiggers@google.com, edumazet@google.com,
intel-wired-lan@lists.osuosl.org, jeffrey.t.kirsher@intel.com,
ktkhai@virtuozzo.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tom@quantonium.net, viro@ZenIV.linux.org.uk
Subject: Re: general protection fault in requeue_rx_msgs
Date: Sat, 13 Apr 2019 02:39:00 -0700 [thread overview]
Message-ID: <0000000000006a8b3505866630b5@google.com> (raw)
In-Reply-To: <0000000000000482ce056d7c1436@google.com>
syzbot has bisected this bug to:
commit 11a350c965cc5ac2f5d0ed1fb336735a0c1a6344
Author: Alan Brady <alan.brady@intel.com>
Date: Fri Dec 29 13:48:33 2017 +0000
i40e: fix typo in function description
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1534b397200000
start commit: 0044cdeb Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1734b397200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1334b397200000
kernel config: https://syzkaller.appspot.com/x/.config?x=968b0b23c7854c0b
dashboard link: https://syzkaller.appspot.com/bug?extid=554266c04a41d1f9754d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=131a208f800000
Reported-by: syzbot+554266c04a41d1f9754d@syzkaller.appspotmail.com
Fixes: 11a350c965cc ("i40e: fix typo in function description")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-04-13 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 8:16 general protection fault in requeue_rx_msgs syzbot
2018-05-31 11:34 ` Kirill Tkhai
2019-04-13 9:39 ` syzbot [this message]
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=0000000000006a8b3505866630b5@google.com \
--to=syzbot+554266c04a41d1f9754d@syzkaller.appspotmail.com \
--cc=alan.brady@intel.com \
--cc=andrewx.bowers@intel.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom@quantonium.net \
--cc=viro@ZenIV.linux.org.uk \
/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).