[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3367219.1676473410@warthog.procyon.org.uk>
Date: Wed, 15 Feb 2023 15:03:30 +0000
From: David Howells <dhowells@...hat.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: dhowells@...hat.com, Jens Axboe <axboe@...nel.dk>,
Al Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@...radead.org>,
Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.cz>,
Jeff Layton <jlayton@...nel.org>,
David Hildenbrand <david@...hat.com>,
Jason Gunthorpe <jgg@...dia.com>,
Logan Gunthorpe <logang@...tatee.com>,
Hillf Danton <hdanton@...a.com>, linux-fsdevel@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Christoph Hellwig <hch@....de>,
John Hubbard <jhubbard@...dia.com>,
linux-unionfs@...r.kernel.org
Subject: Re: [PATCH v14 05/17] overlayfs: Implement splice-read
Miklos Szeredi <miklos@...redi.hu> wrote:
> > + ret = -EINVAL;
> > + if (in->f_flags & O_DIRECT &&
> > + !(real.file->f_mode & FMODE_CAN_ODIRECT))
> > + goto out_fdput;
>
> This is unnecessary, as it was already done in ovl_real_fdget() ->
> ovl_real_fdget_meta() -> ovl_change_flags().
Does that mean ovl_read_iter() and ovl_write_iter() shouldn't be doing it,
then?
David
Powered by blists - more mailing lists