Re: [dm-devel] [PATCH] dm thin: fix NULL pointer exception caused by two concurrent "vgchange -ay -K " processes.

Yes, it is. New patch is as follows: We got a NULL pointer exception when testing the two concurrent "vgchange -ay -K ". panic call trace: PID: 25992 TASK: 883cd7d23500 CPU: 4 COMMAND: "vgchange" #0 [883cd743d600] machine_kexec at 81038fa9 001 [883cd743d660] crash_ke

Re: [dm-devel] [PATCH] dm thin: fix NULL pointer exception caused by two concurrent "vgchange -ay -K " processes.

On Fri, Nov 24, 2017 at 04:59:13PM +0800, monty_pa...@sina.com wrote: > All that we need do is to ensure pool_target registering ops > is the last ops in dm_thin_init. Any other targets wrong too? cache? multipath? snapshot? Alasdair -- dm-devel mailing list dm-devel@redhat.com https

[dm-devel] [PATCH] dm thin: fix NULL pointer exception caused by two concurrent "vgchange -ay -K " processes.

We got a NULL pointer exception when testing the two concurrent "vgchange -ay -K ". panic call trace: PID: 25992 TASK: 883cd7d23500 CPU: 4 COMMAND: "vgchange" #0 [883cd743d600] machine_kexec at 81038fa9 001 [883cd743d660] crash_kexec at 810c5992 002 [