lkml.org 
[lkml]   [2009]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] mmc: prevent dangling block device from accessing stale queues
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!




\
 
 \ /
  Last update: 2009-06-04 21:27    [W:0.050 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site