archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <>
To: Andrew Morton <>
Cc: Andy Walls <>,
	Mauro Carvalho Chehab <>,
	Souptick Joarder <>,
	LKML <>, <>,
	John Hubbard <>
Subject: [PATCH v2 0/2] mm/gup, media/ivtv: introduce pin_user_pages_unlocked
Date: Sun, 31 May 2020 15:48:25 -0700	[thread overview]
Message-ID: <> (raw)


Here is a v2 that includes a small change that follows from Souptick's
review of another very similar patchset (that added
pin_user_pages_locked()) [1].

This applies on top of today's linux.git (5.7-rc7+).

Changes since v1: added an assert-and-return to the corresponding
get_user_pages_unlocked() call, to keep out any externally set
FOLL_PIN flag.

These patches are getting merged via Andrew's linux-mm tree, due to
adding a new pin_user_pages*() variant to gup.c. However, it would be
nice if anyone from IVTV or linux-media could provide some run time
testing, maybe even a Tested-by.

I've run this patchset through non-destructive xfstests, and a few
other things such as LTP. However, I'm not set up for IVTV specific


John Hubbard (2):
  mm/gup: introduce pin_user_pages_unlocked
  ivtv: convert get_user_pages() --> pin_user_pages()

 drivers/media/pci/ivtv/ivtv-udma.c | 19 ++++++-------------
 drivers/media/pci/ivtv/ivtv-yuv.c  | 17 ++++++-----------
 drivers/media/pci/ivtv/ivtvfb.c    |  4 ++--
 include/linux/mm.h                 |  2 ++
 mm/gup.c                           | 23 +++++++++++++++++++++++
 5 files changed, 39 insertions(+), 26 deletions(-)

base-commit: bdc48fa11e46f867ea4d75fa59ee87a7f48be144

             reply	other threads:[~2020-05-31 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 22:48 John Hubbard [this message]
2020-05-31 22:48 ` [PATCH v2 1/2] mm/gup: introduce pin_user_pages_unlocked John Hubbard
2020-05-31 22:48 ` [PATCH v2 2/2] ivtv: convert get_user_pages() --> pin_user_pages() John Hubbard

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 \ \ \ \ \ \ \ \ \ \

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