[dm-devel] kernel BUG at lib/percpu-refcount.c:192

2017-05-18 Thread Marian Csontos
When running `lvm lvcreate --type raid5 --size 4194304B --name meta_r5 LVMTEST12279nqymhamb_vg --yes` there's a warning followed by the bug. Also at [ 192.140142] it looks like there is an uninitialized variable somewhere. env: rawhide, kvm, 2 (V)CPUs lvm2: upstream kernel: 4.12.0-0.rc1.git1

Re: [dm-devel] kernel BUG at lib/percpu-refcount.c:192

2017-06-08 Thread Marian Csontos
Mike, Heinz, help please! RC4 and still present: [ 248.815709] CPU: 0 PID: 21 Comm: rcuos/1 Not tainted 4.12.0-0.rc4.git2.1.fc27.x86_64 #1 [ 248.816841] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2007 ...and it affects RAID1 as well. Is this md wrong or is there a more serious issue? And

Re: [dm-devel] kernel BUG at lib/percpu-refcount.c:192

2017-06-08 Thread Marian Csontos
On 06/08/2017 10:29 AM, Marian Csontos wrote: Mike, Heinz, help please! RC4 and still present: [ 248.815709] CPU: 0 PID: 21 Comm: rcuos/1 Not tainted 4.12.0-0.rc4.git2.1.fc27.x86_64 #1 FYI from changelog: Linux v4.12-rc4-122-gb29794e Commit b29794e from June 6th which is HEAD of master as

Re: [dm-devel] kernel BUG at lib/percpu-refcount.c:192

2017-06-08 Thread Mike Snitzer
On Thu, Jun 08 2017 at 4:29am -0400, Marian Csontos wrote: > Mike, Heinz, help please! > > RC4 and still present: > > [ 248.815709] CPU: 0 PID: 21 Comm: rcuos/1 Not tainted > 4.12.0-0.rc4.git2.1.fc27.x86_64 #1 > [ 248.816841] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2007 > > ...and it a

Re: [dm-devel] kernel BUG at lib/percpu-refcount.c:192

2017-06-08 Thread Shaohua Li
On Thu, Jun 08, 2017 at 09:38:29AM -0400, Mike Snitzer wrote: > On Thu, Jun 08 2017 at 4:29am -0400, > Marian Csontos wrote: > > > Mike, Heinz, help please! > > > > RC4 and still present: > > > > [ 248.815709] CPU: 0 PID: 21 Comm: rcuos/1 Not tainted > > 4.12.0-0.rc4.git2.1.fc27.x86_64 #1 > >

Re: [dm-devel] kernel BUG at lib/percpu-refcount.c:192

2017-06-09 Thread Marian Csontos
On 06/08/2017 07:07 PM, Shaohua Li wrote: Neil fixed a bug in this side recently, which is pretty similar like the reported, I'll push the patch to upstream soon. Could you please try my for-next tree, and check if you still have the issue? Thanks, Shaohua Kernel with the patch applied runs