On Wed, 18 Sep 2013, Zdenek Kabelac wrote: > Dne 18.9.2013 17:57, Mikulas Patocka napsal(a): > > > > > > On Wed, 18 Sep 2013, Zdenek Kabelac wrote: > > > > > Dne 18.9.2013 02:08, Mikulas Patocka napsal(a): > > > > > > > > It's more complicated than that - the original Zdenek's report > > > > shows that the false warning happened on kernel > > > > "3.11.1-300.fc20.x86_64+debug". But I am not able to reproduce the > > > > bug on 3.11, I only reproduced it on 3.5-3.10 kernels. > > > > > > > > Zdenek, could you reproduce the bug on kernel 3.11? > > > > > > > > Mikulas > > > > > > > > > > > > > Since I do not have clean 3.11 at my hands - I've reproduced it with my > > > -rc6 > > > kernel (few patches based on 8495e9c4a9616c9d19f23182d0536485902259db) > > > With enabled kmemleak=on lockdep.prove_locking=1 lockdep.lock_stat=1. > > > > So - try this patch and tell me if it fixes the problem: > > > > Index: linux-2.6-devel/drivers/md/dm-snap-persistent.c > > =================================================================== > > --- linux-2.6-devel.orig/drivers/md/dm-snap-persistent.c 2013-05-10 > > 18:27:31.132358000 +0200 > > +++ linux-2.6-devel/drivers/md/dm-snap-persistent.c 2013-09-17 > > 18:41:39.023940000 +0200 > > @@ -256,7 +256,7 @@ > > */ > > INIT_WORK_ONSTACK(&req.work, do_metadata); > > queue_work(ps->metadata_wq, &req.work); > > - flush_work(&req.work); > > + flush_workqueue(ps->metadata_wq); > > > > return req.result; > > } > > > > Yes - this seems to eliminate reported INFO. OK - so I am submitting the patch for the upstream kernel too. > Though I'm getting curious why some tests are running much much much slower > when kmemleak and lockdep is in use. Because these checks slow things down - that's nothing unexpected. > Zdenek Mikulas --- dm-snapshot: workaround for a lockdep warning The kernel reports a lockdep warning if a snapshot is invalidated because it runs out of space. The lockdep warning was triggered by commit 0976dfc1d0cd80a4e9dfaf87bd8744612bde475a in the kernel 3.5. The warning is false positive. The real cause for the warning is that the lockdep engine treats different instances of md->lock as a single lock. This patch is a workaround - we use flush_workqueue instead of flush_work. This code path is not performance sensitive (it is called only on initialization or invalidation), thus it doesn't matter that we flush the whole workqueue. The real fix for the problem would be to teach the lockdep engine to treat different instances of md->lock as separate locks. Signed-off-by: Mikulas Patocka <mpatocka@xxxxxxxxxx> Acked-by: Alasdair G Kergon <agk@xxxxxxxxxx> Cc: stable@xxxxxxxxxx # 3.5+ Index: linux-2.6-devel/drivers/md/dm-snap-persistent.c =================================================================== --- linux-2.6-devel.orig/drivers/md/dm-snap-persistent.c 2013-05-10 18:27:31.132358000 +0200 +++ linux-2.6-devel/drivers/md/dm-snap-persistent.c 2013-09-17 18:41:39.023940000 +0200 @@ -256,7 +256,7 @@ */ INIT_WORK_ONSTACK(&req.work, do_metadata); queue_work(ps->metadata_wq, &req.work); - flush_work(&req.work); + flush_workqueue(ps->metadata_wq); return req.result; } -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
