From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Subject: Re: [PATCH 1/2] BKL: Remove BKL from default_llseek() Date: Wed, 18 Nov 2009 18:35:54 +0100 Message-ID: <200911181835.55007.oliver@neukum.org> References: <1258560457-15129-1-git-send-email-jblunck@suse.de> <20091118171524.4d2f8cec@lxorguk.ukuu.org.uk> <20091118172730.GD28723@shareable.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Alan Cox , Jan Blunck , linux-fsdevel@vger.kernel.org, "Linux-Kernel Mailinglist" , Andrew Morton , jkacur@redhat.com, Thomas Gleixner , Arnd Bergmann , Christoph Hellwig , =?iso-8859-1?q?Fr=E9d=E9ric_Weisbecker?= , Alexander Viro To: Jamie Lokier Return-path: In-Reply-To: <20091118172730.GD28723@shareable.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Am Mittwoch, 18. November 2009 18:27:30 schrieb Jamie Lokier: > > No. Your logic is flawed > > > > The BKL is protected something here - it protects the change of offset > > with respect to other BKL users within drivers. The question is what if > > anything in any other driver code depends upon the BKL and uses it to > > protect f_pos. Probably very little if anything but a grep for f_pos > > through the drivers might not be a bad idea before assuming this. Very > > few touch f_pos except in their own llseek method. > > Of course, drivers shouldn't be using f_pos outside their llseek > method, as they should all behave the same with pread/pwrite as with > llseek+read/write. Might not a driver update f_pos after read/write? Regards Oliver