BTW. this patch is no longer needed on 3.11 because md->io_lock was removed there, so the false lockdep warning doesn't happen. So we need to get this patch to stable trees 3.5 to 3.10, but not upstream. How to push the patch there without pushing it upstream? Mikulas On Tue, 17 Sep 2013, Mikulas Patocka wrote: > 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> > 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
