Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932267AbVK1WoL (ORCPT ); Mon, 28 Nov 2005 17:44:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932269AbVK1WoL (ORCPT ); Mon, 28 Nov 2005 17:44:11 -0500 Received: from omx2-ext.sgi.com ([192.48.171.19]:28388 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S932267AbVK1WoK (ORCPT ); Mon, 28 Nov 2005 17:44:10 -0500 Date: Tue, 29 Nov 2005 09:43:57 +1100 From: Nathan Scott To: Christoph Hellwig Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com Subject: Re: [PATCH] remove broken direct I/O size ioctl Message-ID: <20051129094357.G7047179@wobbly.melbourne.sgi.com> References: <20051128222501.GA7238@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20051128222501.GA7238@lst.de>; from hch@lst.de on Mon, Nov 28, 2005 at 11:25:01PM +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 849 Lines: 21 On Mon, Nov 28, 2005 at 11:25:01PM +0100, Christoph Hellwig wrote: > This ioctl tries to second guess direct I/O parameters which aren't > a filesystem drivers business and shouldn't be exposed as an ioctl > to start with. Unfortunately there are some applications that will now start to see errors from this ioctl if we go this route - whereas before they would've been "functional", now they will break. So, I think we need a different solution here. Yes, I agree its a stupid call to have on Linux, but here we are, and apps ported straight from IRIX have been made to use this. cheers. -- Nathan - 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/