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.0711281711210.3641-100000@iolanthe.rowland.org>
Date:	Wed, 28 Nov 2007 17:14:51 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Raymano Garibaldi <raymano@...nos.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Denys Vlasenko <vda.linux@...glemail.com>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] [BUG] USB_PERSIST

On Tue, 27 Nov 2007, Raymano Garibaldi wrote:

> Hi Alan,
> 
> Here's what I got after compiling kernel with CONFIG_USB_PERSIST and
> CONFIG_USB_DEBUG both enabled. The attached files are:
> 
> config - shows the .config file used when compiling kernel 2.6.23.9
> 
> sysandmount.txt - shows mounts and the state of persist for all usb
> devices right before suspending.
> 
> dmesg_attached.txt - dmesg right after resuming when the USB device
> remained attached while machine was suspend
> 
> dmesg_detachedandreattached.txt - dmesg right after resuming when the
> USB device was detached while suspended and then reattached before
> resuming.

This all looks okay.  Earlier you wrote:

> I have tried this. Simply turning off CONFIG_USB_PERSIST doesn't work.
> In this case the USB drive file system is unmounted on resume, even if
> the drive remained plugged in during suspend.

But the logs you just posted show that the filesystem _does_ remain 
mounted after resume, provided you don't unplug the drive.  At least 
that's what it looked like -- it was hard to tell for sure because each 
logfile contained multiple suspend/resume cycles with varying outcomes.

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