On Mon, 14 Aug 2017, Jorg Bornschein wrote: > August 13, 2017 4:44 PM, "Coly Li" <colyli@xxxxxxx> wrote: > > Hi Coly, > > > were you able to reproduce my problem? Hi Jorg, Can you convert those memory offsets to line numbers in the backtrace with something like `gdb vmlinuz` and `list *(bch_bucket_alloc+0xa5/0x350)` ? (Someone correct me if the gdb list command is slightly different, it has been a while.) It sounds like a registration race, maybe a simple spinlock or mutex is appropriate here. -- Eric Wheeler > > > j > > > > On 2017/8/13 下午11:40, Jorg Bornschein wrote: > > > >> August 13, 2017 4:27 PM, "Coly Li" <colyli@xxxxxxx> wrote: > >> > >> Hi Coly, > >> > >>> Could you please give me some hint how the /dev/dm- nodes are created ? > >>> I will try to reproduce it on my hardware. > >>> > >>> Thanks for the report. > >> > >> I created them with 'cryptsetup luksFormat ...', IIRC. When I run 'cryptsetup luksDump' I get: > >> > >> Version: 1 > >> Cipher name: aes > >> Cipher mode: xts-plain64 > >> Hash spec: sha256 > >> Payload offset: 4096 > >> MK bits: 256 > >> MK digest: <STUFF> > >> MK salt: <STUFF> > >> MK iterations: 400000 > >> UUID: 81a8d12e-9309-4317-b447-ab3c86e2f7ea > >> > >> Key Slot 0: ENABLED > >> Iterations: 3200000 > >> Salt: <STUFF> > >> Key material offset: 8 > >> AF stripes: 4000 > >> > >> and this is the contents of my /etc/crypttab: > >> > >> # <name> <device> <password> <options> > >> crypted-sdb /dev/sdb1 /etc/cryptfs.key > >> crypted-sdc /dev/sdc1 /etc/cryptfs.key > >> crypted-sdd /dev/sdd1 /etc/cryptfs.key > >> crypted-sde /dev/sde1 /etc/cryptfs.key > > > > Oh, I don't use cryptsetup before, let me try ... Thanks for the hint :-) > > > > Coly Li > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html >
