[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49r3xf28qn.fsf@segfault.boston.devel.redhat.com>
Date: Thu, 06 Nov 2014 18:46:08 -0500
From: Jeff Moyer <jmoyer@...hat.com>
To: Milosz Tanski <milosz@...in.com>
Cc: linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>,
Christoph Hellwig <hch@...radead.org>,
linux-fsdevel@...r.kernel.org, linux-aio@...ck.org,
Mel Gorman <mgorman@...e.de>,
Volker Lendecke <Volker.Lendecke@...net.de>,
Tejun Heo <tj@...nel.org>, "Theodore Ts'o" <tytso@....edu>,
Al Viro <viro@...iv.linux.org.uk>, linux-api@...r.kernel.org,
Michael Kerrisk <mtk.manpages@...il.com>,
linux-arch@...r.kernel.org, ceph-devel@...r.kernel.org,
fuse-devel@...ts.sourceforge.net, linux-nfs@...r.kernel.org,
ocfs2-devel@....oracle.com, linux-mm@...ck.org
Subject: Re: [PATCH v5 7/7] fs: add a flag for per-operation O_DSYNC semantics
Milosz Tanski <milosz@...in.com> writes:
> - if (type == READ && (flags & RWF_NONBLOCK))
> - return -EAGAIN;
> + if (type == READ) {
> + if (flags & RWF_NONBLOCK)
> + return -EAGAIN;
> + } else {
> + if (flags & RWF_DSYNC)
> + return -EINVAL;
> + }
Minor nit, but I'd rather read something that looks like this:
if (type == READ && (flags & RWF_NONBLOCK))
return -EAGAIN;
else if (type == WRITE && (flags & RWF_DSYNC))
return -EINVAL;
I won't lose sleep over it, though.
Reviewed-by: Jeff Moyer <jmoyer@...hat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists