netdev - Re: [PATCH 0/4] usbnet: avoiding access auto-suspended device

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20121103.145207.70028483679120460.davem@davemloft.net>
Date:	Sat, 03 Nov 2012 14:52:07 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ming.lei@...onical.com
Cc:	gregkh@...uxfoundation.org, oneukum@...e.de,
	netdev@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH 0/4] usbnet: avoiding access auto-suspended device

From: Ming Lei <ming.lei@...onical.com>
Date: Mon, 29 Oct 2012 15:45:05 +0800

> Thip patchset avoids accessing auto-suspended device in ioctl path,
> which is generally triggered by some network utility(ethtool, ifconfig,
> ...)
> 
> Most of network devices have the problem, but as discussed in the
> thread:
> 
> 	http://marc.info/?t=135054860600003&r=1&w=2
> 
> the problem should be solved inside driver.
> 
> Considered that only smsc75xx and smsc95xx calls usbnet_read_cmd()
> and usbnet_write_cmd() inside its resume and suspend callback, the
> patcheset introduce the nopm version of the two functions which
> should be called only in the resume and suspend callback. So we
> can solve the problem by runtime resuming device before doing
> control message things.
> 
> The patchset is against 3.7.0-rc3-next-20121029, and has been tested
> OK on smsc95xx usbnet device.

This series doesn't apply against net-next, as there have been
changes to the smsc drivers meanwhile.

You'll need to respin this series against net-next.
--
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