linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] clean up kernel read/write helpers
Date: Fri, 10 Jul 2020 18:00:58 +0200	[thread overview]
Message-ID: <20200710160058.GA540798@infradead.org> (raw)

(note that the new WARN_ONs in combination with syzcaller already found a
missing input validation in 9p.  The fix should be on your way through
the maintainer ASAP)

The following changes since commit dcde237b9b0eb1d19306e6f48c0a4e058907619f:

  Merge tag 'perf-tools-fixes-2020-07-07' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux (2020-07-07 15:38:53 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/hch/misc.git tags/cleanup-kernel_read_write

for you to fetch changes up to 775802c0571fb438cd4f6548a323f9e4cb89f5aa:

  fs: remove __vfs_read (2020-07-08 08:27:57 +0200)

----------------------------------------------------------------
cleanup in-kernel read and write operations

Reshuffle the (__)kernel_read and (__)kernel_write helpers, and ensure
all users of in-kernel file I/O use them if they don't use iov_iter
based methods already.

----------------------------------------------------------------
Christoph Hellwig (11):
      cachefiles: switch to kernel_write
      autofs: switch to kernel_write
      bpfilter: switch to kernel_write
      fs: unexport __kernel_write
      fs: check FMODE_WRITE in __kernel_write
      fs: implement kernel_write using __kernel_write
      fs: remove __vfs_write
      fs: add a __kernel_read helper
      integrity/ima: switch to using __kernel_read
      fs: implement kernel_read using __kernel_read
      fs: remove __vfs_read

 fs/autofs/waitq.c            |   2 +-
 fs/cachefiles/rdwr.c         |   2 +-
 fs/read_write.c              | 131 +++++++++++++++++++++++++------------------
 include/linux/fs.h           |   2 +-
 net/bpfilter/bpfilter_kern.c |   2 +-
 security/integrity/iint.c    |  14 +----
 6 files changed, 80 insertions(+), 73 deletions(-)


             reply	other threads:[~2020-07-10 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 16:00 Christoph Hellwig [this message]
2020-07-10 16:55 ` [GIT PULL] clean up kernel read/write helpers pr-tracker-bot

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=20200710160058.GA540798@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).