Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757676AbZKSCkY (ORCPT ); Wed, 18 Nov 2009 21:40:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757586AbZKSCkN (ORCPT ); Wed, 18 Nov 2009 21:40:13 -0500 Received: from mail2.shareable.org ([80.68.89.115]:49508 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757298AbZKSCkM (ORCPT ); Wed, 18 Nov 2009 21:40:12 -0500 Date: Thu, 19 Nov 2009 02:40:08 +0000 From: Jamie Lokier To: Alan Cox Cc: Oliver Neukum , 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 Subject: Re: [PATCH 1/2] BKL: Remove BKL from default_llseek() Message-ID: <20091119024008.GB15128@shareable.org> References: <1258560457-15129-1-git-send-email-jblunck@suse.de> <20091118171524.4d2f8cec@lxorguk.ukuu.org.uk> <20091118172730.GD28723@shareable.org> <200911181835.55007.oliver@neukum.org> <20091118175003.GF28723@shareable.org> <20091118181606.1c8caab1@lxorguk.ukuu.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091118181606.1c8caab1@lxorguk.ukuu.org.uk> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 978 Lines: 23 Alan Cox wrote: > O> But nowadays, even that doesn't happen. sys_read() and sys_write() > > make a copy of f_pos using file_pos_read(), so drivers cannot see the > > value change during the call - except for their own change. > > > > I find myself wondering why the VFS isn't responsible for the position > > update instead of the driver... Would it be a valid cleanup to move > > it from the driver to VFS? > > And how would you adjust it. Not all devices have a bytes read == offset > relationship. The VFS doesn't know enough. That was implicit in my question: Are there any seekable devices where bytes read != offset delta, and if yes, is that correct behaviour, a bug, or a silly interface that should go away? -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/