netdev - Re: future developments of usbnet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1105091130440.2002-100000@iolanthe.rowland.org>
Date:	Mon, 9 May 2011 11:31:16 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Ming Lei <tom.leiming@...il.com>
cc:	Oliver Neukum <oliver@...kum.org>, <netdev@...r.kernel.org>,
	<linux-usb@...r.kernel.org>
Subject: Re: future developments of usbnet

On Mon, 9 May 2011, Ming Lei wrote:

> Hi,
> 
> 2011/5/9 Oliver Neukum <oliver@...kum.org>:
> 
> > Do we really need to avoid it, or do we just need to recover?
> > If avoidance is needed, should we use NAPI?
> 
> IMO, OOM can recover it certainly but with much cost, so we should
> avoid the case. I don't think NAPI can avoid it, because NAPI will
> cause skb to be allocated without any limit if there are packets
> coming, still no chance left for usbnet_bh to handle and free these
> SKBs.

How do other network drivers handle this problem?  Can the same 
strategy be used?

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html