On Tue, May 18, 2010 at 18:23, Nick Bowler <nbowler@xxxxxxxxxxxxxxxx> wrote: > On 16:21 Tue 18 May , Kay Sievers wrote: >> On Tue, May 18, 2010 at 15:25, Nick Bowler <nbowler@xxxxxxxxxxxxxxxx> wrote: >> > On 07:08 Tue 18 May , Kay Sievers wrote: >> >> What does: >> >> cat /sys/class/block/sr0/../../evt_media_change >> >> print for this device? >> > >> > Prints 1. >> >> Oh, seems to be an AN capable device, which actually really sends events. :) >> >> I don't know if that works, never tried, but if you chmod the >> evt_media_change file to 0664. and write 0 to it, does it still behave >> the same? > > I can successfully chmod and write 0 to that file, and it reads back as > 0, but the behaviour remains the same (the blkid rules are uncommented), > and the disk never spins down. Ok, as said, it was just a try. Thanks for the test. The kernel seems not to filter events based on that mask. So a fix for this would be in the kernel, to either provide information about the source of the event, or to be able to suppress these AN event, which have no obvious meaning. Tejun, an AN capable SATA optical drive seems to send AN events with every open(). For userspace these look the same as the media changed events, and cause a loop when udev checks if there is a new media. Any ideas if these AN events are expected, or useful for anything? David, this is stuff we might need to cover with udisks in the future to handle AN properly. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
