[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2337531.1673953876@warthog.procyon.org.uk>
Date: Tue, 17 Jan 2023 11:11:16 +0000
From: David Howells <dhowells@...hat.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: dhowells@...hat.com, Al Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.cz>,
Jeff Layton <jlayton@...nel.org>,
Logan Gunthorpe <logang@...tatee.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 01/34] vfs: Unconditionally set IOCB_WRITE in call_write_iter()
Christoph Hellwig <hch@...radead.org> wrote:
> I suspect the best is to:
>
> - rename init_sync_kiocb to init_kiocb
> - pass a new argument for the direction to it. I'm not entirely
> sure if flags is a good thing, or an explicit READ/WRITE might be
> better because it's harder to get wrong, even if a the compiler
> might generate worth code for it.
So something like:
init_kiocb(kiocb, file, WRITE);
init_kiocb(kiocb, file, READ);
David
Powered by blists - more mailing lists