From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alessio Igor Bogani <abogani@texware.it>
Subject: [PATCH 0/5 -tip] umount_begin BKL pushdown
Date: Thu, 23 Apr 2009 21:12:00 +0200
Message-ID: <1240513925-5603-1-git-send-email-abogani@texware.it>
Cc: Jonathan Corbet <corbet@lwn.net>,
	=?utf-8?q?Fr=C3=A9d=C3=A9ric=20Weisbecker?= <fweisbec@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	LFSDEV <linux-fsdevel@vger.kernel.org>,
	Alessio Igor Bogani <abogani@texware.it>
To: Ingo Molnar <mingo@elte.hu>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail-fx0-f158.google.com ([209.85.220.158]:61329 "EHLO
	mail-fx0-f158.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751632AbZDWTMO (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 23 Apr 2009 15:12:14 -0400
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Push the BKL acquisition from vfs to every specific filesystems
with hope that it can be eliminated in a second moment.

The first 4 patches add BKL lock into umount_begin() functions (for
the filesystems that have this handler). The last one remove
lock_kernel()/unlock_kernel() from fs/namespace.c (the only point
that invoke umount_begin() funtcions).