Re: [PATCH] mmc: prevent dangling block device from accessing stalequeues

[Stefan Bader]

Matt Fleming wrote:
> On Thu, Jun 04, 2009 at 09:00:42PM +0200, Stefan Bader wrote:
> > Hm, not sure this is what you wanted to know... On the launchpad report 
> > there are logs which I took with lots of printk's enabled. This shows that 
> > after resume the queue receives a request from mmcblk0 (which no longer 
> > exists) but uses the same pointer as mmcblk1 which was just created.
>
> Maybe I'm missing something, but why is the device instance being
> destroyed during a suspend? E.g why do you have mmcblk0 before suspend and
> mmcblk1 after suspend?

That is the way mmcblock works  (without unsafe resume set) in conjunction with 
( probably ) slow userspace. On suspend the block device is removed. But the 
mount is cleaned by (in that case hald) doing a forced unmount. The timeing 
seems to be that the unmount part is partially done on the way up.

--

When all other means of communication fail, try words!


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/