Alexander Gran <[EMAIL PROTECTED]> wrote: > > while umounting an ext2 partition on a usb hdd I'm getting: > scheduling while atomic: umount/0x10000001/14941 > [<c0451392>] schedule+0x5f2/0x600 > [<c0451cc7>] cond_resched+0x27/0x40 > [<c0140af1>] invalidate_mapping_pages+0x81/0xe0 > [<c015b27d>] kill_bdev+0xd/0x20 > [<c015b315>] __set_blocksize+0x85/0xa0 > [<c015bba0>] __bd_release+0x70/0x80 > [<c015c458>] __close_bdev_excl+0x8/0x10 > [<c015a100>] deactivate_super+0x50/0x80 > [<c016f82b>] sys_umount+0x3b/0x90 > [<c0148c20>] do_munmap+0x120/0x150 > [<c016f895>] sys_oldumount+0x15/0x20 > [<c010300b>] sysenter_past_esp+0x54/0x75
hm, yes, that was a bug in blockdev-fixes-race-between-mount-umount.patch, but that patch got dropped because Linus fixed things differently. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
