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
| ||
|
Message-Id: <1351992594-12818-1-git-send-email-ming.lei@canonical.com> Date: Sun, 4 Nov 2012 09:29:49 +0800 From: Ming Lei <ming.lei@...onical.com> To: "David S. Miller" <davem@...emloft.net>, Greg Kroah-Hartman <gregkh@...uxfoundation.org> Cc: Oliver Neukum <oneukum@...e.de>, netdev@...r.kernel.org, linux-usb@...r.kernel.org Subject: [PATCH v1 0/5] usbnet: avoiding access auto-suspended device 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-20121102, and has been tested OK on smsc95xx usbnet device. Change logs: V1: - rebased on 3.7.0-rc3-next-20121102, only patch 4/5 changed - fix one memory leak during smsc95xx_suspend, patch 3/5 added drivers/net/usb/smsc75xx.c | 133 +++++++++++++++++++++++++--------------- drivers/net/usb/smsc95xx.c | 146 ++++++++++++++++++++++++++++---------------- drivers/net/usb/usbnet.c | 72 ++++++++++++++++++++-- include/linux/usb/usbnet.h | 4 ++ 4 files changed, 248 insertions(+), 107 deletions(-) Thanks, -- Ming Lei -- 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
Powered by blists - more mailing lists