[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1240556813-8739-1-git-send-email-abogani@texware.it>
Date: Fri, 24 Apr 2009 09:06:52 +0200
From: Alessio Igor Bogani <abogani@...ware.it>
To: Alexander Viro <viro@...iv.linux.org.uk>
Cc: Jonathan Corbet <corbet@....net>,
Frédéric Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
LKML <linux-kernel@...r.kernel.org>,
LFSDEV <linux-fsdevel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>, Matthew Wilcox <matthew@....cx>,
Alessio Igor Bogani <abogani@...ware.it>
Subject: [PATCH 0/1] vfs: umount_begin BKL pushdown v2
Push the BKL acquisition from vfs to every specific filesystems
with hope that it can be eliminated in a second moment.
Filesystems, which support umount_begin(), changed by this patch
are 9p, nfs, cifs and fuse.
Changes:
Collapsed all patches into only one as requested by Al Viro.
Moved CIFS_SB() down into BKL protected zone as requested by Matthew Wilcox.
It is hard to say if tcon (into cifs's umount_begin() function) should be
protected by BKL. Up to now umount_begin() is always called with BKL held
so in uncertainty I maintain same logic. So I moved unlock_kernel() to at
the bottom of that function as requested by Al Viro and Matthew Wilcox.
Notes:
About cifs's umount_begin() function I suspect that a deadlock or circular
locking dependency can happens into kill-the-BKL tree if that patch is applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists