netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+e77327e34cdc8c36b7d3@syzkaller.appspotmail.com>
To: brett.creeley@amd.com, davem@davemloft.net, drivers@pensando.io,
	 edumazet@google.com, hengqi@linux.alibaba.com, horms@kernel.org,
	 jiri@resnulli.us, kuba@kernel.org, linux-kernel@vger.kernel.org,
	 netdev@vger.kernel.org, pabeni@redhat.com,
	shannon.nelson@amd.com,  syzkaller-bugs@googlegroups.com,
	vladimir.oltean@nxp.com
Subject: Re: [syzbot] [net?] general protection fault in coalesce_fill_reply
Date: Wed, 26 Jun 2024 21:59:02 -0700	[thread overview]
Message-ID: <00000000000054b7cc061bd7fdeb@google.com> (raw)
In-Reply-To: <0000000000006293f0061bca5cea@google.com>

syzbot has bisected this issue to:

commit 55a3982ec721dabd5a4c2f16bfb03deb032e45c2
Author: Shannon Nelson <shannon.nelson@amd.com>
Date:   Wed Jun 19 00:32:55 2024 +0000

    ionic: check for queue deadline in doorbell_napi_work

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11fc181a980000
start commit:   50b70845fc5c Merge branch 'add-ethernet-driver-for-tehuti-..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15fc181a980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e78fc116033e0ab7
dashboard link: https://syzkaller.appspot.com/bug?extid=e77327e34cdc8c36b7d3
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1599901a980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1429e301980000

Reported-by: syzbot+e77327e34cdc8c36b7d3@syzkaller.appspotmail.com
Fixes: 55a3982ec721 ("ionic: check for queue deadline in doorbell_napi_work")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-06-27  4:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 12:43 [syzbot] [net?] general protection fault in coalesce_fill_reply syzbot
2024-06-26 12:44 ` Eric Dumazet
2024-06-26 15:36   ` Heng Qi
2024-06-27  4:59 ` 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=00000000000054b7cc061bd7fdeb@google.com \
    --to=syzbot+e77327e34cdc8c36b7d3@syzkaller.appspotmail.com \
    --cc=brett.creeley@amd.com \
    --cc=davem@davemloft.net \
    --cc=drivers@pensando.io \
    --cc=edumazet@google.com \
    --cc=hengqi@linux.alibaba.com \
    --cc=horms@kernel.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shannon.nelson@amd.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vladimir.oltean@nxp.com \
    /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).