linux-kernel - [PATCH] staging: usbip: Notify usb core of port status changes

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>] [day] [month] [year] [list]

Message-ID: <20100921153140.GA4635@quark.vpn.nusquama.org>
Date:	Tue, 21 Sep 2010 17:31:40 +0200
From:	Max Vozeler <mvz@...eler.com>
To:	Greg Kroah-Hartman <gregkh@...e.de>
Cc:	hirofuchi@...rs.sourceforge.net, hschauhan@...ltrace.org,
	"Robert P. J. Day" <rpjday@...shcourse.ca>,
	"Brian G. Merrell" <bgmerrell@...ell.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Marco Lancione <marco@...ikam.com>,
	Luc Jalbert <ljalbert@...ikam.com>
Subject: [PATCH] staging: usbip: Notify usb core of port status changes

This patch changes vhci to behave like dummy and 
other hcds when disconnecting a device.

Previously detaching a device from the root hub 
did not notify the usb core of the disconnect and
left the device visible.

Signed-off-by: Max Vozeler <mvz@...eler.com>
Reported-by: Marco Lancione <marco@...ikam.com>
Tested-by: Luc Jalbert <ljalbert@...ikam.com>
Cc: stable@...nel.org
---
 drivers/staging/usbip/vhci_hcd.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/drivers/staging/usbip/vhci_hcd.c b/drivers/staging/usbip/vhci_hcd.c
index 0574d84..832608d 100644
--- a/drivers/staging/usbip/vhci_hcd.c
+++ b/drivers/staging/usbip/vhci_hcd.c
@@ -164,6 +164,8 @@ void rh_port_disconnect(int rhport)
 	 * spin_unlock(&vdev->ud.lock); */
 
 	spin_unlock_irqrestore(&the_controller->lock, flags);
+
+	usb_hcd_poll_rh_status(vhci_to_hcd(the_controller));
 }
 
 
-- 
1.7.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/