From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git - more set_fs elimination
Date: Fri, 15 Sep 2017 00:00:41 +0100 [thread overview]
Message-ID: <20170914230040.GS5426@ZenIV.linux.org.uk> (raw)
Christoph's "use kernel_read and friends rather than open-coding
set_fs()" series.
The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98:
Linux 4.13-rc7 (2017-08-27 17:20:40 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.set_fs
for you to fetch changes up to 9725d4cef62229b4ec4c912e0db0761e7d400650:
fs: unexport vfs_readv and vfs_writev (2017-09-04 19:05:16 -0400)
----------------------------------------------------------------
Christoph Hellwig (17):
ashmem: switch to ->read_iter
autofs4: switch autofs4_write to __kernel_write
fs: move kernel_write to fs/read_write.c
fs: move kernel_read to fs/read_write.c
fs: fix kernel_read prototype
fs: fix kernel_write prototype
fs: make the buf argument to __kernel_write a void pointer
serial2002: switch serial2002_tty_write to kernel_{read/write}
mm/nommu: switch do_mmap_private to kernel_read
net/9p: switch p9_fd_read to kernel_write
btrfs: switch write_buf to kernel_write
mconsole: switch to kernel_read
gadget/f_mass_storage: stop messing with the address limit
lustre: switch to kernel_write
fs: unexport __vfs_read/__vfs_write
fs: unexport vfs_read and vfs_write
fs: unexport vfs_readv and vfs_writev
arch/mips/kernel/elf.c | 12 ++----
arch/um/drivers/mconsole_kern.c | 7 +---
arch/x86/ia32/ia32_aout.c | 4 +-
drivers/media/pci/cx25821/cx25821-audio-upstream.c | 13 +++----
drivers/mtd/nand/nandsim.c | 4 +-
drivers/staging/android/ashmem.c | 29 ++++-----------
drivers/staging/comedi/drivers/serial2002.c | 24 +++---------
drivers/staging/lustre/lnet/libcfs/tracefile.c | 10 +----
.../staging/lustre/lustre/obdclass/kernelcomm.c | 7 +---
drivers/target/target_core_alua.c | 3 +-
drivers/target/target_core_file.c | 2 +-
drivers/target/target_core_pr.c | 3 +-
drivers/usb/gadget/function/f_mass_storage.c | 21 +++--------
fs/autofs4/waitq.c | 9 +----
fs/binfmt_aout.c | 3 +-
fs/binfmt_elf.c | 23 +++++++-----
fs/binfmt_elf_fdpic.c | 17 +++++----
fs/binfmt_flat.c | 18 +++------
fs/binfmt_misc.c | 5 ++-
fs/btrfs/send.c | 18 ++-------
fs/coda/dir.c | 5 ++-
fs/ecryptfs/read_write.c | 4 +-
fs/exec.c | 24 ++----------
fs/read_write.c | 43 ++++++++++++++++------
fs/splice.c | 16 --------
include/linux/fs.h | 9 ++---
kernel/acct.c | 2 +-
kernel/sysctl_binary.c | 21 +++++++----
mm/nommu.c | 7 +---
net/9p/trans_fd.c | 14 +++----
security/keys/big_key.c | 6 ++-
31 files changed, 147 insertions(+), 236 deletions(-)
reply other threads:[~2017-09-14 23:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170914230040.GS5426@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.