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: Sun, 12 Sep 2010 11:49:29 +0200 From: Maxim Levitsky <maximlevitsky@...il.com> To: linux-kernel <linux-kernel@...r.kernel.org> Cc: Jens Axboe <axboe@...nel.dk> Subject: [REGRESSION] cdrom drive doesn't detect removal Hi, After a switch between hal to devkit stack, a different strategy of detecting a cdrom removal was applied. Instead of polling it, userspace just tells the kernel not to lock the dour (/proc/sys/dev/cdrom/lock) and as soon as user removes the disk, udev notifies the userspace and it unmounts it. Since CDROMs are readonly this is perfectly safe and fits the same procedure used for all other removable disks. (usb, flash cards, etc..) (Well, most cdroms aren't really read-only these days, but state of packet writing is so sad these days that is doesn't matter). However 2.6.36 doesn't detect that removal. According to udevadm monitor --property no uevents are send on removal. My feeling is that this is BKL fallout. I of course use new libata stack, so my cdrom driver is sr. Best regards, Maxim Levitsky -- 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