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
| ||
|
Date: Thu, 3 Aug 2006 08:29:03 +0200 From: Willy Tarreau <w@....eu> To: Pete Zaitcev <zaitcev@...hat.com> Cc: benjamin.cherian.kernel@...il.com, linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net Subject: Re: Bug with USB proc_bulk in 2.4 kernel On Wed, Aug 02, 2006 at 11:00:58PM -0700, Pete Zaitcev wrote: > Replace the semaphore exclusive_access with an open-coded lock for > the special use. The lock can be taken for: read, write, and both. > This way, two bulk URBs can be submitted simultaneously with ioctl > USBDEVFS_BULK: one read and one write. Such access was possible > before 2.4.28. > > Signed-off-By: Pete Zaitcev <zaitcev@...hat.com> > > --- > > The semaphore was introduced in 2.4.28 for the purpose of exclusion > between access from device.c (cat /proc/bus/usb/devices), devio.c > through libusb, and in-kernel driver. Currently, only usb-storage > observes the locking protocol. The most popular device which locks > in case of simultaneous access is TEAC CD-210PU. Perfect. Patch queued, thanks Pete. Willy - 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