| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 04 Jun 2009 21:23:31 +0200 From: Stefan Bader <stefan.bader@...onical.com> To: Matt Fleming <matt@...sole-pimps.org> CC: Pierre Ossman <pierre@...man.eu>, Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org, Andy Whitcroft <apw@...onical.com> Subject: Re: [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! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists