From: Christoph Hellwig Subject: Re: O_NONBLOCK for regular files Date: Thu, 18 Mar 2004 08:45:54 +0000 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040318084554.A25642@infradead.org> References: <20040318083628.A25565@infradead.org> <20040318084259.GH31500@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from phoenix.infradead.org ([213.86.99.234]:8456 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S262037AbUCRIp5 (ORCPT ); Thu, 18 Mar 2004 03:45:57 -0500 To: viro@parcelfarce.linux.theplanet.co.uk Content-Disposition: inline In-Reply-To: <20040318084259.GH31500@parcelfarce.linux.theplanet.co.uk>; from viro@parcelfarce.linux.theplanet.co.uk on Thu, Mar 18, 2004 at 08:42:59AM +0000 List-Id: linux-fsdevel.vger.kernel.org On Thu, Mar 18, 2004 at 08:42:59AM +0000, viro@parcelfarce.linux.theplanet.co.uk wrote: > How do they handle fcntl() (re)setting O_NONBLOCK? The code checks file->f_flags & O_NONBLOCK, so it's exactly the same as for all other uses.