[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YL7/Qv/CBvXIUlKT@infradead.org>
Date: Tue, 8 Jun 2021 06:25:22 +0100
From: Christoph Hellwig <hch@...radead.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@...radead.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
David Sterba <dsterba@...e.com>,
Miklos Szeredi <miklos@...redi.hu>,
Anton Altaparmakov <anton@...era.com>,
David Howells <dhowells@...hat.com>,
Matthew Wilcox <willy@...radead.org>,
Pavel Begunkov <asml.silence@...il.com>
Subject: Re: [RFC][PATCHSET] iov_iter work
On Mon, Jun 07, 2021 at 04:35:46PM -0700, Linus Torvalds wrote:
> Thinking more about this thing, I think it means that what we *should*
> do is simply just
>
> void iov_iter_init(struct iov_iter *i, unsigned int direction,
> const struct iovec *iov, unsigned long nr_segs,
> size_t count)
> {
> WARN_ON_ONCE(direction & ~(READ | WRITE));
> iWARN_ON_ONCE(uaccess_kernel());
Yes, exactly! (except for the spurious i above, of course).
Powered by blists - more mailing lists