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]
Date:	Tue, 5 Sep 2006 12:59:39 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Randy.Dunlap" <rdunlap@...otime.net>
cc:	USB development list <linux-usb-devel@...ts.sourceforge.net>,
	Linux-pm mailing list <linux-pm@...ts.osdl.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] [RFC] USB device persistence across suspend-to-disk

On Tue, 5 Sep 2006, Randy.Dunlap wrote:

> > +Setting the "persist=y" module parameter for usbcore will cause the
> 
>                 persist=1 ??

Either will work.

> > +kernel to work around these issues.  If usbcore is build into the
> 
> s/build/built/

Got it, thanks.

> > +main kernel instead of as a separate module, you can put
> > +"usbcore.persist=1" on the boot command line.  You can also change the
> > +kernel's behavior on the fly using sysfs: Type
> > +
> > +	echo y >/sys/module/usbcore/parameters/persist
> 
> Does sysfs treat 'y' as '1'?
> Anyway, it would be Good to be consistent.

Yes; I'll change everything to 'y'.

> > +structure.  In effect, the kernel treats the device as though it had
> > +merely been reset instead of unplugged.
> 
> so does the USB device also retain its same USB address?

It does.  It didn't seem worthwhile to mention that point, however.

> > -			dev->have_langid = -1;
> > +			dev->have_langid = 1;

> Different patch (?).

When this is submitted for inclusion, that change will be broken out into 
a separate patch.

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