Jun'ichi Nomura wrote: > Patrick McHardy wrote: > >>Jun'ichi Nomura wrote: >> >>>Are you using other dm modules such as dm-multipath, dm-mirror >>>or dm-snapshot? >>>If so, can you take the output of 'dmsetup table' and 'dmsetup ls'? >> >>No other modules. >> >> >>>Do you have a reliable way to reproduce the oops which I can try? >> >>"/etc/init.d/cryptdisk start" (debian) on a luks partition triggered >>it for me. > > > With today's git HEAD (commit 49c13b51a15f1ba9f6d47e26e4a3886c4f3931e2), > I tried the following but could not reproduce the oops here. > # cryptsetup luksFormat /dev/sdb1 > # cryptsetup luksOpen /dev/sdb1 c > # mkfs.ext3 /dev/mapper/c > <mount it and do some I/O>
I put in the patch again and it doesn't oops anymore, so sorry for the false alarm. I did got the oops I pasted several times before that though, I'll keep an eye on it and try to gather more information in case it happens again. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
