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.0806271628390.1304-100000@netrider.rowland.org>
Date:	Fri, 27 Jun 2008 16:35:59 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Lukas Hejtmanek <xhejtman@....muni.cz>
cc:	Greg KH <greg@...ah.com>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re: 2.6.26-rc1 regression since 2.6.25 - problem in 2.6.26-rc8 again

On Fri, 27 Jun 2008, Lukas Hejtmanek wrote:

> > What does usbmon reveal when you dock the laptop again and then plug in
> > the disk (see Documentation/usb/usbmon.txt)?
> 
> attached as 1-26.mon.out (2.6.26-rc8)
>  
> > Can you provide a comparable usbmon log for 2.6.25?
> 
> attached as 1-25.mon.out

This is very confusing.  It appears that the two usbmon logs don't show 
the same actions on your part.

Let's try to keep this as simple as possible.  We'll consider a single 
fixed course of action:

	Make sure the disk isn't mounted and isn't in use.

	Start collecting the usbmon log.

	Remove the disk.

	Wait at least 10 seconds.

	Undock the laptop.

	Wait at least 10 seconds.

	Dock the laptop again.

	Wait at least 10 seconds.

	Plug in the disk.

	Stop the usbmon log.

(The reason for those 10-second delays is because the USB stack will 
automatically suspend an idle hub after a few seconds of inactivity.)

Do exactly the same thing under both operating system versions, and 
then we should have suitably comparable logs.

Alan Stern

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ