From: "Bjørn Mork" <bjorn@mork.no>
To: Emil Goode <emilgoode@gmail.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
"'Igor Gnatenko'" <i.gnatenko.brain@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Ming Lei <ming.lei@canonical.com>,
Mark Brown <broonie@linaro.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Glen Turner <gdt@gdt.id.au>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: asix: fix bad header length bug
Date: Fri, 07 Feb 2014 10:38:04 +0100 [thread overview]
Message-ID: <87wqh7i7pf.fsf@nemi.mork.no> (raw)
In-Reply-To: <20140206224121.GB5251@lianli> (Emil Goode's message of "Thu, 6 Feb 2014 23:41:21 +0100")
Emil Goode <emilgoode@gmail.com> writes:
> On Thu, Feb 06, 2014 at 03:28:13PM +0000, David Laight wrote:
>> From: Igor Gnatenko
>> > On Thu, 2014-02-06 at 13:56 +0100, Emil Goode wrote:
>> > > The AX88772B occasionally send rx packets that cross urb boundaries
>> > > and the remaining partial packet is sent with no header.
>> > > When the buffer with a partial packet is of less number of octets
>> > > than the value of hard_header_len the buffer is discarded by the
>> > > usbnet module. This is causing dropped packages and error messages
>> > > in dmesg.
> I will do some more digging in the code, but the test of skb->len
> against hard_header_len is done already in the completion callback
> function passed to usb_fill_bulk_urb so it seems that buffers of less
> than hard_header_len number of octets will be dropped regardless.
I am pretty sure you are right about this bug. And the exact same
solution is already used by the cx82310_eth minidriver, so I don't see
the problem. Your fix is fine IMHO. But you should apply it to all the
devices using asix_rx_fixup_common(), not just the ax88772 ones.
You could maybe make this a usbnet flag instead and create a generic
solution in usbnet, but frankly I believe the number of flags and their
meaning have exceeded drivers authors capabilities a long time ago. At
least mine, which are quite limited ;-)
An example of that problem is another bloody obvious bug I noticed while
looking at this driver: The 'struct driver_info ax88178_info' points to
asix_rx_fixup_common without setting the FLAG_MULTI_PACKET. This will
result in usbnet rx_process() calling usbnet_skb_return() on skbs which
are already consumed by the minidriver. Not a big problem, but will
give some odd results. But if you allow skbs shorter than ETH_HLEN to
slip through then it might go boom, so you should probably fix that as
well.
Bjørn
next prev parent reply other threads:[~2014-02-07 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 12:56 [PATCH] net: asix: fix bad header length bug Emil Goode
2014-02-06 13:19 ` Igor Gnatenko
2014-02-06 15:28 ` David Laight
2014-02-06 22:41 ` Emil Goode
2014-02-07 9:38 ` Bjørn Mork [this message]
2014-02-07 13:53 ` Emil Goode
2014-02-07 14:40 ` David Laight
2014-02-06 13:37 ` David Laight
2014-02-06 15:02 ` Emil Goode
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=87wqh7i7pf.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=David.Laight@ACULAB.COM \
--cc=broonie@linaro.org \
--cc=davem@davemloft.net \
--cc=emilgoode@gmail.com \
--cc=gdt@gdt.id.au \
--cc=i.gnatenko.brain@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=netdev@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