On Fri, May 12, 2006 at 10:27:29AM -0700, Andrew Vasquez wrote:
> On Fri, 12 May 2006, Erik Mouw wrote:
> > I tracked it down with git bisect. The culprit is this commit:
> >
> > 56cf6504fc1c0c221b82cebc16a444b684140fb7 is first bad commit
> > diff-tree 56cf6504fc1c0c221b82cebc16a444b684140fb7 (from
> > d98550e334715b2d9e45f8f0f4e1608720108640)
> > Author: Russell King <[email protected]>
> > Date: Fri May 5 17:57:52 2006 +0100
> >
> > [BLOCK] Fix oops on removal of SD/MMC card
> >
> > The block layer keeps a reference (driverfs_dev) to the struct
> > device associated with the block device, and uses it internally
> > for generating uevents in block_uevent.
> >
> > Block device uevents include umounting the partition, which can
> > occur after the backing device has been removed.
> ...
>
> THat's really weird... I reported a completely unrelated problem some
> days ago:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114728598328769&w=2
AFAICS it's the same bug. Apparently you can trigger it with any scsi
host driver.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
