Linux-Fsdevel Archive on
help / color / mirror / Atom feed
From: Christoph Hellwig <>
To: David Laight <>
Cc: "" <>,
	"" <>,
	"" <>,
	Jens Axboe <>,
	"David S. Miller" <>,
	Al Viro <>,
	linux-fsdevel <>
Subject: Re: [PATCH 1/9 next] mm:process_vm_access Call import_iovec() instead of rw_copy_check_uvector()
Date: Mon, 21 Sep 2020 15:09:35 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Sep 15, 2020 at 02:55:08PM +0000, David Laight wrote:
> This is the only direct call of rw_copy_check_uvector().
> Removing it lets rw_copy_check_uvector() be inlined into
> import_iovec() and the horrid calling conventions fixed.

This looks sensible, but as-is will create a warning when actually
this code.

This is the variant I picked up as a prep patch for the compat
iovec handling, which passes the relevant LTP tests:

      reply	other threads:[~2020-09-21 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 14:55 David Laight
2020-09-21 14:09 ` Christoph Hellwig [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH 1/9 next] mm:process_vm_access Call import_iovec() instead of rw_copy_check_uvector()' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).