public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakemuksen spammiosote <jhroska@byterapers.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usbnet.c, buf.overrun crash-bugfix, Kernel 2.6.12-rc1
Date: Thu, 24 Mar 2005 20:13:59 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0503242006160.767@byterapers.com> (raw)
In-Reply-To: <200503240857.28594.david-b@pacbell.net>

On Thu, 24 Mar 2005, David Brownell wrote:
> On Thursday 24 March 2005 8:05 am, Jakemuksen spammiosote wrote:
>> Atleast versions 2.6.5 - 2.6.12-rc1 crash if an USB device using usbnet
>> sends oversized packet. Such packets occur most likely with broken
> Care to mention what device(s) you saw this with?   And what HCD?

I can't tell about the device(NDA), and don't remember the HCD and I can 
check it only after holidays.

>> +       if (unlikely((skb->tail + urb->actual_length) > skb->end)) {
> This logic looks wrong.  If that ever happens, surely the problem is
> that the rx_submit() code submitted an urb with transfer_size that
> mismatched the SKB.  The host controller isn't allowed to overrun the

Sounds reasonable. So, I'll go thru the HCD code instead if the 
responsibility is there. Am i the first one to run into such crash 
situation? If so, perhaps it's not ever worthy to fix in mainstream 
kernel, as the device causes the crash under very specific - 
'abusing' one might say, situation only.


  reply	other threads:[~2005-03-24 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 16:05 [PATCH] usbnet.c, buf.overrun crash-bugfix, Kernel 2.6.12-rc1 Jakemuksen spammiosote
2005-03-24 16:57 ` David Brownell
2005-03-24 18:13   ` Jakemuksen spammiosote [this message]
2005-03-24 18:23     ` David Brownell

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=Pine.LNX.4.61.0503242006160.767@byterapers.com \
    --to=jhroska@byterapers.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.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