All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Fri, 17 Nov 2017 02:50:32 +0000	[thread overview]
Message-ID: <20171117025032.GK21978@ZenIV.linux.org.uk> (raw)

	* bio_{map,copy}_user_iov() series; those are cleanups - fixes from
the same pile went into mainline (and stable) in late September.
	* fs/iomap.c iov_iter-related fixes
	* new primitive - iov_iter_for_each_range(); apply a function to
kernel-mapped segments of an iov_iter.  Usable for kvec and bvec ones,
the latter does kmap()/kunmap() around the callback.  _Not_ usable for
iovec- or pipe-backed iov_iter; the latter is not hard to fix if the need
ever appears, the former is by design.  Another related primitive will
have to wait for the next cycle - it passes page + offset + size instead
of pointer + size, and that one will be usable for everything _except_
kvec.  Unfortunately, that one didn't get exposure in -next yet, so...
	* a bit more lustre iov_iter work, including a use case for
iov_iter_for_each_range() (checksum calculation).
	* vhost/scsi leak fix in failure exit.
	* misc cleanups and detritectomy...

The following changes since commit 1cfd0ddd82232804e03f3023f6a58b50dfef0574:

  bio_copy_user_iov(): don't ignore ->iov_offset (2017-10-10 23:55:14 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.iov_iter

for you to fetch changes up to cfe057f7db1ff026c8db75469a3f9ba9736e1975:

  iomap_dio_actor(): fix iov_iter bugs (2017-10-11 22:38:02 -0400)

----------------------------------------------------------------
Al Viro (21):
      bio_map_user_iov(): switch to iov_iter_get_pages()/iov_iter_advance()
      ... and with iov_iter_get_pages_alloc() it becomes even simpler
      don't rely upon subsequent bio_add_pc_page() calls failing
      bio_map_user_iov(): move alignment check into the main loop
      bio_map_user_iov(): get rid of the iov_for_each()
      blk_rq_map_user_iov(): move iov_iter_advance() down
      move more stuff down into bio_copy_user_iov()
      bio_copy_from_iter(): get rid of copying iov_iter
      bio_map_user_iov(): get rid of copying iov_iter
      bio_copy_user_iov(): saner bio size calculation
      bio_alloc_map_data(): do bmd->iter setup right there
      kill iov_shorten()
      orangefs: remove detritus from struct orangefs_kiocb_s
      xen: don't open-code iov_iter_kvec()
      lnet_return_rx_credits_locked: don't abuse list_entry
      new primitive: iov_iter_for_each_range()
      fix a page leak in vhost_scsi_iov_to_sgl() error recovery
      vhost/scsi: switch to iov_iter_get_pages()
      lustre: switch struct ksock_conn to iov_iter
      switch ksocknal_lib_recv_...() to use of iov_iter_for_each_range()
      iomap_dio_actor(): fix iov_iter bugs

 block/bio.c                                        | 192 ++++++++-------------
 block/blk-map.c                                    |   7 -
 .../staging/lustre/lnet/klnds/socklnd/socklnd.c    |   4 +-
 .../staging/lustre/lnet/klnds/socklnd/socklnd.h    |   9 +-
 .../staging/lustre/lnet/klnds/socklnd/socklnd_cb.c | 157 ++++-------------
 .../lustre/lnet/klnds/socklnd/socklnd_lib.c        |  99 +++--------
 drivers/staging/lustre/lnet/lnet/lib-move.c        |   2 +-
 drivers/vhost/scsi.c                               |  73 +++-----
 drivers/xen/pvcalls-back.c                         |  16 +-
 fs/iomap.c                                         |  24 ++-
 fs/orangefs/orangefs-kernel.h                      |   6 -
 fs/read_write.c                                    |  21 ---
 include/linux/bio.h                                |   4 +-
 include/linux/uio.h                                |   6 +-
 lib/iov_iter.c                                     |  22 +++
 15 files changed, 202 insertions(+), 440 deletions(-)

             reply	other threads:[~2017-11-17  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17  2:50 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-11  0:41 [git pull] vfs.git iov_iter Al Viro
2019-03-12 21:04 ` Linus Torvalds
2019-03-12 22:20 ` 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=20171117025032.GK21978@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.