From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Ian Kent <raven@themaw.net>, David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: clean up kernel_{read,write} & friends v2
Date: Wed, 20 May 2020 17:59:40 +0200 [thread overview]
Message-ID: <20200520155940.GA4313@lst.de> (raw)
In-Reply-To: <20200513065656.2110441-1-hch@lst.de>
ping?
On Wed, May 13, 2020 at 08:56:42AM +0200, Christoph Hellwig wrote:
> Hi Al,
>
> this series fixes a few issues and cleans up the helpers that read from
> or write to kernel space buffers, and ensures that we don't change the
> address limit if we are using the ->read_iter and ->write_iter methods
> that don't need the changed address limit.
>
> Changes since v1:
> - __kernel_write must not take sb_writers
> - unexported __kernel_write
---end quoted text---
next prev parent reply other threads:[~2020-05-20 15:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 6:56 clean up kernel_{read,write} & friends v2 Christoph Hellwig
2020-05-13 6:56 ` [PATCH 01/14] cachefiles: switch to kernel_write Christoph Hellwig
2020-05-15 15:21 ` David Howells
2020-05-13 6:56 ` [PATCH 02/14] autofs: " Christoph Hellwig
2020-05-14 8:25 ` Ian Kent
2020-05-13 6:56 ` [PATCH 03/14] bpfilter: " Christoph Hellwig
2020-05-13 6:56 ` [PATCH 04/14] fs: unexport __kernel_write Christoph Hellwig
2020-05-13 6:56 ` [PATCH 05/14] fs: check FMODE_WRITE in __kernel_write Christoph Hellwig
2020-05-13 6:56 ` [PATCH 06/14] fs: remove the call_{read,write}_iter functions Christoph Hellwig
2020-05-13 6:56 ` [PATCH 07/14] fs: implement kernel_write using __kernel_write Christoph Hellwig
2020-05-13 6:56 ` [PATCH 08/14] fs: remove __vfs_write Christoph Hellwig
2020-05-13 6:56 ` [PATCH 09/14] fs: don't change the address limit for ->write_iter in __kernel_write Christoph Hellwig
2020-05-13 6:56 ` [PATCH 10/14] fs: add a __kernel_read helper Christoph Hellwig
2020-05-13 6:56 ` [PATCH 11/14] integrity/ima: switch to using __kernel_read Christoph Hellwig
2020-05-13 6:56 ` [PATCH 12/14] fs: implement kernel_read " Christoph Hellwig
2020-05-13 6:56 ` [PATCH 13/14] fs: remove __vfs_read Christoph Hellwig
2020-05-13 6:56 ` [PATCH 14/14] fs: don't change the address limit for ->read_iter in __kernel_read Christoph Hellwig
[not found] ` <20200516030436.19448-1-hdanton@sina.com>
2020-05-18 6:42 ` [PATCH 09/14] fs: don't change the address limit for ->write_iter in __kernel_write Christoph Hellwig
2020-05-20 15:59 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-28 5:40 clean up kernel_{read,write} & friends v2 Christoph Hellwig
2020-05-28 18:51 ` Linus Torvalds
2020-05-28 18:57 ` Sedat Dilek
2020-05-28 19:22 ` Joe Perches
2020-05-28 19:33 ` Al Viro
2020-05-28 19:44 ` Matthew Wilcox
2020-05-28 20:06 ` Al Viro
2020-05-28 20:14 ` Deucher, Alexander
2020-05-28 20:18 ` Joe Perches
2020-05-28 20:29 ` Dave Airlie
2020-05-28 21:03 ` Joe Perches
2020-05-28 20:17 ` David Howells
2020-05-28 21:20 ` Casey Schaufler
2020-05-29 13:08 ` David Laight
2020-05-29 19:19 ` Linus Torvalds
2020-05-29 22:02 ` Casey Schaufler
2020-06-05 6:36 ` Philippe Mathieu-Daudé
2020-06-05 15:00 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200520155940.GA4313@lst.de \
--to=hch@lst.de \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.