From: Christoph Hellwig Subject: O_NONBLOCK for regular files Date: Thu, 18 Mar 2004 08:36:28 +0000 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040318083628.A25565@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from phoenix.infradead.org ([213.86.99.234]:2312 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S262006AbUCRIg3 (ORCPT ); Thu, 18 Mar 2004 03:36:29 -0500 Received: from hch by phoenix.infradead.org with local (Exim 4.30 #5 (Red Hat Linux)) id 1B3t0u-0006eQ-Np for linux-fsdevel@vger.kernel.org; Thu, 18 Mar 2004 08:36:28 +0000 To: linux-fsdevel@vger.kernel.org Content-Disposition: inline List-Id: linux-fsdevel.vger.kernel.org Guy, any opinion on whether we should allow O_NONBLOCK for regular files? XFS currently has this in as a leftover from IRIX, it's used to to allow the HSM support code in XFS (not in the kernel.org code due to the horrible design, just in the oss.sgi.com tree) to return EAGAIN to the nfs server so it doesn't block all nfsd threads on possible long-enduring HSM operations. People want to bring that thing over to Linux now which brought that O_NONBLOCK thing on my radar. I don't see any direct problems with this thing, but I don't want it as an undocumented XFS extension.