> > > Code; c0160d0f <d_unhash+f/70> <=====
> It would be much more useful if the oops code were to dump the
> text preceding the exception EIP rather than after it, actually.
I think I already mentioned what the stack trace is for this oops:
for me, it is sd_detach -> driverfs_remove_partitions ->
put_device -> driverfs_remove_dir -> driverfs_rmdir -> d_unhash.
I have seen lots of other oopses related to driverfs.
Submitted a stopgap patch to prevent some of them, but withdrew it
when it became clear that even the ugly stopgap did not prevent all.
This driverfs partition stuff is messy. The code paths where partitions
are created are very different from those where partitions are removed,
and it can easily happen that a partition is removed that was never
created, leading to an oops.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/