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 iov_iter pile
Date: Mon, 12 Dec 2022 00:35:04 +0000 [thread overview]
Message-ID: <Y5Z3OMYJOMxQqXQf@ZenIV> (raw)
Minor conflicts with erofs branch; conflicting changes in this one
are all of form s/READ/ITER_DEST/ in iov_iter_xarray() calls.
The following changes since commit eb7081409f94a9a8608593d0fb63a1aa3d6f95d8:
Linux 6.1-rc6 (2022-11-20 16:02:16 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-iov_iter
for you to fetch changes up to de4eda9de2d957ef2d6a8365a01e26a435e958cb:
use less confusing names for iov_iter direction initializers (2022-11-25 13:01:55 -0500)
----------------------------------------------------------------
iov_iter work; most of that is about getting rid of
direction misannotations and (hopefully) preventing
more of the same for the future.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (12):
get rid of unlikely() on page_copy_sane() calls
csum_and_copy_to_iter(): handle ITER_DISCARD
[s390] copy_oldmem_kernel() - WRITE is "data source", not destination
[fsi] WRITE is "data source", not destination...
[infiniband] READ is "data destination", not source...
[s390] zcore: WRITE is "data source", not destination...
[s390] memcpy_real(): WRITE is "data source", not destination...
[target] fix iov_iter_bvec() "direction" argument
[vhost] fix 'direction' argument of iov_iter_{init,bvec}()
[xen] fix "direction" argument of iov_iter_kvec()
iov_iter: saner checks for attempt to copy to/from iterator
use less confusing names for iov_iter direction initializers
arch/s390/kernel/crash_dump.c | 2 +-
arch/s390/mm/maccess.c | 2 +-
arch/x86/kernel/cpu/microcode/intel.c | 2 +-
arch/x86/kernel/crash_dump_64.c | 2 +-
crypto/testmgr.c | 4 +--
drivers/acpi/pfr_update.c | 2 +-
drivers/block/drbd/drbd_main.c | 2 +-
drivers/block/drbd/drbd_receiver.c | 2 +-
drivers/block/loop.c | 12 ++++----
drivers/block/nbd.c | 10 +++----
drivers/char/random.c | 4 +--
drivers/fsi/fsi-sbefifo.c | 6 ++--
drivers/infiniband/ulp/rtrs/rtrs-clt.c | 2 +-
drivers/isdn/mISDN/l1oip_core.c | 2 +-
drivers/misc/vmw_vmci/vmci_queue_pair.c | 6 ++--
drivers/net/ppp/ppp_generic.c | 2 +-
drivers/nvme/host/tcp.c | 4 +--
drivers/nvme/target/io-cmd-file.c | 4 +--
drivers/nvme/target/tcp.c | 2 +-
drivers/s390/char/zcore.c | 2 +-
drivers/scsi/sg.c | 2 +-
drivers/target/iscsi/iscsi_target_util.c | 4 +--
drivers/target/target_core_file.c | 4 +--
drivers/usb/usbip/usbip_common.c | 2 +-
drivers/vhost/net.c | 6 ++--
drivers/vhost/scsi.c | 10 +++----
drivers/vhost/vhost.c | 6 ++--
drivers/vhost/vringh.c | 4 +--
drivers/vhost/vsock.c | 4 +--
drivers/xen/pvcalls-back.c | 8 ++---
fs/9p/vfs_addr.c | 4 +--
fs/9p/vfs_dir.c | 2 +-
fs/9p/xattr.c | 4 +--
fs/afs/cmservice.c | 2 +-
fs/afs/dir.c | 2 +-
fs/afs/file.c | 4 +--
fs/afs/internal.h | 4 +--
fs/afs/rxrpc.c | 10 +++----
fs/afs/write.c | 4 +--
fs/aio.c | 4 +--
fs/btrfs/ioctl.c | 4 +--
fs/ceph/addr.c | 4 +--
fs/ceph/file.c | 4 +--
fs/cifs/connect.c | 6 ++--
fs/cifs/file.c | 4 +--
fs/cifs/fscache.c | 4 +--
fs/cifs/smb2ops.c | 4 +--
fs/cifs/transport.c | 6 ++--
fs/coredump.c | 2 +-
fs/erofs/fscache.c | 6 ++--
fs/fscache/io.c | 2 +-
fs/fuse/ioctl.c | 4 +--
fs/netfs/io.c | 6 ++--
fs/nfs/fscache.c | 4 +--
fs/nfsd/vfs.c | 4 +--
fs/ocfs2/cluster/tcp.c | 2 +-
fs/orangefs/inode.c | 8 ++---
fs/proc/vmcore.c | 6 ++--
fs/read_write.c | 12 ++++----
fs/seq_file.c | 2 +-
fs/splice.c | 10 +++----
include/linux/uio.h | 3 ++
io_uring/net.c | 14 ++++-----
io_uring/rw.c | 10 +++----
kernel/trace/trace_events_user.c | 2 +-
lib/iov_iter.c | 50 ++++++++++++++++++--------------
mm/madvise.c | 2 +-
mm/page_io.c | 4 +--
mm/process_vm_access.c | 2 +-
net/9p/client.c | 2 +-
net/bluetooth/6lowpan.c | 2 +-
net/bluetooth/a2mp.c | 2 +-
net/bluetooth/smp.c | 2 +-
net/ceph/messenger_v1.c | 4 +--
net/ceph/messenger_v2.c | 14 ++++-----
net/compat.c | 3 +-
net/ipv4/tcp.c | 4 +--
net/netfilter/ipvs/ip_vs_sync.c | 2 +-
net/smc/smc_clc.c | 6 ++--
net/smc/smc_tx.c | 2 +-
net/socket.c | 12 ++++----
net/sunrpc/socklib.c | 6 ++--
net/sunrpc/svcsock.c | 4 +--
net/sunrpc/xprtsock.c | 6 ++--
net/tipc/topsrv.c | 2 +-
net/tls/tls_device.c | 4 +--
net/xfrm/espintcp.c | 2 +-
security/keys/keyctl.c | 4 +--
88 files changed, 224 insertions(+), 214 deletions(-)
next reply other threads:[~2022-12-12 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 0:35 Al Viro [this message]
2022-12-13 3:49 ` [git pull] vfs.git iov_iter pile 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=Y5Z3OMYJOMxQqXQf@ZenIV \
--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.