Summary: | sys-kernel/gentoo-sources: No uevent when loop devices get removed (loopbacks persist in udisks when gone) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ByrneG <byrneg+gentoo-bugzilla> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=c3473c63542d53740f175f3a515257ae159e998b | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | backported patch to generate "change" uevent for loop device |
Description
ByrneG
2010-07-14 09:09:25 UTC
Patch here: http://people.freedesktop.org/~david/0001-Generate-change-uevent-for-loop-device.patch Applied to Linux GIT tree if I'm not mistaken here: http://lkml.org/lkml/2010/5/21/327 So.. This is a bug in the kernel, not in udisks itself... reassigning to gentoo-sources maintainers Created attachment 240647 [details]
backported patch to generate "change" uevent for loop device
Can you apply this to gentoo-sources-2.6.34-r2 and let me know if it fixes your issue.
Let me know if you need help applying it.
I applied the patch, recompiled the kernel and re-tested. The issue has not been resolved by this patch. The test was as follows: 1. $ mkdosfs -C floppy.img 1440 2. $ mkdir flpy 3. $ sudo mount -o loop floppy.img ./flpy/ # Gnome adds the "flpy" device and a "1.5 MB Filesystem" device to "Places" 4. $ sudo umount ./flpy # Gnome removes the "flpy" device, but the "1.5 MB Filesystem" remains. 5. $ sudo losetup -a # No results displayed (with or without sudo) 6. $ udisks --enumerate # The list includes " /org/freedesktop/UDisks/devices/loop0" There seems to be no way to unmount or detach the loop device from udisks, regardless of privileges, as the device isn't mounted... $ udisks --unmount /dev/loop0 Unmount failed: Device is not mounted Let me know if you need any additional info. Please test with gentoo-sources-2.6.35 Kernel 2.6.35 resolves this issue. (In reply to comment #5) > Kernel 2.6.35 resolves this issue. > closing as fixed by 2.6.35 then |