[lkml]   [2012]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH] virtio_blk: Checking "private_data" to avoid kernel panic when hotplugging
On Wed, Mar 28, 2012 at 11:40:33AM +0800, Ren Mingxin wrote:
> Hi,
> On guest with upstream's kernel(3.3.0-rc7), I
> mounted virtblk as:
> a) # mkfs /dev/vda
> b) # mount /dev/vda /mnt
> c) # cd /mnt
> Then I did hotplug for virtblk via virsh on host as:
> a) # sudo virsh detach-disk guest vda
> b) # sudo virsh attach-disk guest /media/data/test.img vda
> I encountered guest's kernel panic (*probability *
> *event*)whose backtrace liked this:

Any news here? Managed to trace?
Does this still happen with 3.4-rc2?
There's a chance you are hitting a race fixed by

If it's still not fixed it might make sense to enable slab debugging -
we might have a use after free here.


 \ /
  Last update: 2012-04-09 09:59    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean