linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: syzbot <syzbot+ce366e2b8296e25d84f5@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, davem@davemloft.net,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, oliver@neukum.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: divide error in cdc_ncm_update_rxtx_max
Date: Tue, 17 Sep 2019 17:46:20 +0200	[thread overview]
Message-ID: <87d0fzlycz.fsf@miraculix.mork.no> (raw)
In-Reply-To: <00000000000018e4250592c043c3@google.com> (syzbot's message of "Tue, 17 Sep 2019 07:09:00 -0700")

syzbot <syzbot+ce366e2b8296e25d84f5@syzkaller.appspotmail.com> writes:

> syzbot has tested the proposed patch but the reproducer still
> triggered crash:
> divide error in usbnet_update_max_qlen
>
> cdc_ncm 5-1:1.0: setting tx_max = 16384
> divide error: 0000 [#1] SMP KASAN
> CPU: 1 PID: 1737 Comm: kworker/1:2 Not tainted 5.3.0-rc7+ #0
> Hardware name: Google Google Compute Engine/Google Compute Engine,
> BIOS Google 01/01/2011
> Workqueue: usb_hub_wq hub_event
> RIP: 0010:usbnet_update_max_qlen drivers/net/usb/usbnet.c:344 [inline]
> RIP: 0010:usbnet_update_max_qlen+0x231/0x370 drivers/net/usb/usbnet.c:338

Sure, but that's another error already fixed by Oliver..

I guess this fix worked.  But I believe we should see if this is a more
generic issue than just this single driver/bug.  I fear it is...



Bjørn

      reply	other threads:[~2019-09-17 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 13:29 divide error in cdc_ncm_update_rxtx_max syzbot
2019-09-17 13:52 ` Bjørn Mork
2019-09-17 14:09   ` syzbot
2019-09-17 15:46     ` Bjørn Mork [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=87d0fzlycz.fsf@miraculix.mork.no \
    --to=bjorn@mork.no \
    --cc=andreyknvl@google.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=syzbot+ce366e2b8296e25d84f5@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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).