| 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: <200701151724.42831.oneukum@suse.de> Date: Mon, 15 Jan 2007 17:24:42 +0100 From: Oliver Neukum <oneukum@...e.de> To: linux-usb-devel@...ts.sourceforge.net Cc: Alan Stern <stern@...land.harvard.edu>, Oliver Neukum <oliver@...kum.org>, icxcnika@....tar.cc, linux-kernel@...r.kernel.org Subject: Re: [linux-usb-devel] 2.6.20-rc4: usb somehow broken Am Montag, 15. Januar 2007 17:03 schrieb Alan Stern: > On Mon, 15 Jan 2007, Oliver Neukum wrote: > > Upon further thought, a module parameter won't do as the problem > > will arise without a driver loaded. A sysfs parameter turns the whole > > affair into a race condition. Will you set the guard parameter before the > > autosuspend logic strikes? > > Unfortunately this leaves only the least attractive solution. > > There could be a mixed approach: a builtin blacklist that is extensible > via a procfs- or sysfs-based interface. If you want to ask with a lot of bug reports which blacklist was loaded, then we could. > Note that we actually have two problems to contend with. Some devices > must never be autosuspended at all (they disconnect when resuming), and > others need a reset after resuming. Do those who can be brought back with a reset need to be listed at all? Error handling is not a bad idea. Regards Oliver - 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