[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201119180315.GB24054@infradead.org>
Date: Thu, 19 Nov 2020 18:03:15 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Michal Kubecek <mkubecek@...e.cz>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@...radead.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] eventfd: convert to ->write_iter()
On Thu, Nov 19, 2020 at 07:00:19PM +0100, Michal Kubecek wrote:
> While eventfd ->read() callback was replaced by ->read_iter() recently by
> commit 12aceb89b0bc ("eventfd: convert to f_op->read_iter()"), ->write()
> was not replaced.
>
> Convert also ->write() to ->write_iter() to make the interface more
> consistent and allow non-blocking writes from e.g. io_uring. Also
> reorganize the code and return value handling in a similar way as it was
> done in eventfd_read().
But this patch does not allow non-blocking writes. I'm really
suspicious as you're obviously trying to hide something from us.
Powered by blists - more mailing lists