summaryrefslogtreecommitdiffstats
path: root/kernel/power
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@g5.osdl.org>2006-05-12 18:42:09 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2006-05-12 18:42:09 -0700
commit032ebf2620ef99a4fedaa0f77dc2272095ac5863 (patch)
tree18a341e1548a304efea7543c715d23255ada6fa3 /kernel/power
parent18552b8f227bddf569dade5c69798a37839ea913 (diff)
downloadop-kernel-dev-032ebf2620ef99a4fedaa0f77dc2272095ac5863.zip
op-kernel-dev-032ebf2620ef99a4fedaa0f77dc2272095ac5863.tar.gz
Alternative fix for MMC oops on unmount after removal
Make sure to clear the driverfs_dev pointer when we do del_gendisk() (on disk removal), so that other users that may still have a ref to the disk won't try to use the stale pointer. Also move the KOBJ_REMOVE uevent handler up, so that the uevent still has access to the driverfs_dev data. This all should hopefully fix the problems with MMC umounts after device removals that caused commit 56cf6504fc1c0c221b82cebc16a444b684140fb7 and its reversal (1a2acc9e9214699a99389e323e6686e9e0e2ca67). Original problem reported by Todd Blumer and others. Acked-by: Greg KH <gregkh@suse.de> Cc: Russell King <rmk+lkml@arm.linux.org.uk> Cc: James Bottomley <James.Bottomley@SteelEye.com> Cc: Erik Mouw <erik@harddisk-recovery.com> Cc: Andrew Vasquez <andrew.vasquez@qlogic.com> Cc: Todd Blumer <todd@sdgsystems.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'kernel/power')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud