From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: [PULL] topic/iomem-mmap-vs-gup
Date: Mon, 3 May 2021 21:15:08 +0200 [thread overview]
Message-ID: <YJBHiRiCGzojk25U@phenom.ffwll.local> (raw)
Hi Linus,
It's still the same topic branch as last merge window, but the name isn't
fitting all that well anymore :-)
Anyway here's a small pull for you to ponder, now that the big ones are
all through. It's been in -next almost the entire cycle, I've only done
some non-code rebases due to the -rc1 fumble and to fix some commit
message typos.
Christoph Hellwig also looked at these and aside from wanting to outright
remove it all didn't have objections.
topic/iomem-mmap-vs-gup-2021-05-03:
unexport follow_pfn
Follow-up to my pull from last merge window: kvm and vfio lost their
very unsafe use of follow_pfn, this appropriately marks up the very
last user for some userptr-as-buffer use-cases in media. There was
some resistance to outright removing it, maybe we can do this in a few
releases.
Cheers, Daniel
The following changes since commit 0d02ec6b3136c73c09e7859f0d0e4e2c4c07b49b:
Linux 5.12-rc4 (2021-03-21 14:56:43 -0700)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm tags/topic/iomem-mmap-vs-gup-2021-05-03
for you to fetch changes up to ac8b8400620a4b0d9ca903ee9ad440bec736f5fa:
mm: unexport follow_pfn (2021-04-08 16:54:38 +0200)
----------------------------------------------------------------
unexport follow_pfn
Follow-up to my pull from last merge window: kvm and vfio lost their
very unsafe use of follow_pfn, this appropriately marks up the very
last user for some userptr-as-buffer use-cases in media. There was
some resistance to outright removing it, maybe we can do this in a few
releases.
----------------------------------------------------------------
Daniel Vetter (3):
mm: Add unsafe_follow_pfn
media/videobuf1|2: Mark follow_pfn usage as unsafe
mm: unexport follow_pfn
drivers/media/common/videobuf2/frame_vector.c | 2 +-
drivers/media/v4l2-core/videobuf-dma-contig.c | 2 +-
include/linux/mm.h | 4 +--
mm/memory.c | 46 +++++++++++++++++----------
mm/nommu.c | 28 ++++++++++++----
security/Kconfig | 13 ++++++++
6 files changed, 68 insertions(+), 27 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: [PULL] topic/iomem-mmap-vs-gup
Date: Mon, 3 May 2021 21:15:08 +0200 [thread overview]
Message-ID: <YJBHiRiCGzojk25U@phenom.ffwll.local> (raw)
Hi Linus,
It's still the same topic branch as last merge window, but the name isn't
fitting all that well anymore :-)
Anyway here's a small pull for you to ponder, now that the big ones are
all through. It's been in -next almost the entire cycle, I've only done
some non-code rebases due to the -rc1 fumble and to fix some commit
message typos.
Christoph Hellwig also looked at these and aside from wanting to outright
remove it all didn't have objections.
topic/iomem-mmap-vs-gup-2021-05-03:
unexport follow_pfn
Follow-up to my pull from last merge window: kvm and vfio lost their
very unsafe use of follow_pfn, this appropriately marks up the very
last user for some userptr-as-buffer use-cases in media. There was
some resistance to outright removing it, maybe we can do this in a few
releases.
Cheers, Daniel
The following changes since commit 0d02ec6b3136c73c09e7859f0d0e4e2c4c07b49b:
Linux 5.12-rc4 (2021-03-21 14:56:43 -0700)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm tags/topic/iomem-mmap-vs-gup-2021-05-03
for you to fetch changes up to ac8b8400620a4b0d9ca903ee9ad440bec736f5fa:
mm: unexport follow_pfn (2021-04-08 16:54:38 +0200)
----------------------------------------------------------------
unexport follow_pfn
Follow-up to my pull from last merge window: kvm and vfio lost their
very unsafe use of follow_pfn, this appropriately marks up the very
last user for some userptr-as-buffer use-cases in media. There was
some resistance to outright removing it, maybe we can do this in a few
releases.
----------------------------------------------------------------
Daniel Vetter (3):
mm: Add unsafe_follow_pfn
media/videobuf1|2: Mark follow_pfn usage as unsafe
mm: unexport follow_pfn
drivers/media/common/videobuf2/frame_vector.c | 2 +-
drivers/media/v4l2-core/videobuf-dma-contig.c | 2 +-
include/linux/mm.h | 4 +--
mm/memory.c | 46 +++++++++++++++++----------
mm/nommu.c | 28 ++++++++++++----
security/Kconfig | 13 ++++++++
6 files changed, 68 insertions(+), 27 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-samsung-soc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [PULL] topic/iomem-mmap-vs-gup
Date: Mon, 3 May 2021 21:15:08 +0200 [thread overview]
Message-ID: <YJBHiRiCGzojk25U@phenom.ffwll.local> (raw)
Hi Linus,
It's still the same topic branch as last merge window, but the name isn't
fitting all that well anymore :-)
Anyway here's a small pull for you to ponder, now that the big ones are
all through. It's been in -next almost the entire cycle, I've only done
some non-code rebases due to the -rc1 fumble and to fix some commit
message typos.
Christoph Hellwig also looked at these and aside from wanting to outright
remove it all didn't have objections.
topic/iomem-mmap-vs-gup-2021-05-03:
unexport follow_pfn
Follow-up to my pull from last merge window: kvm and vfio lost their
very unsafe use of follow_pfn, this appropriately marks up the very
last user for some userptr-as-buffer use-cases in media. There was
some resistance to outright removing it, maybe we can do this in a few
releases.
Cheers, Daniel
The following changes since commit 0d02ec6b3136c73c09e7859f0d0e4e2c4c07b49b:
Linux 5.12-rc4 (2021-03-21 14:56:43 -0700)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm tags/topic/iomem-mmap-vs-gup-2021-05-03
for you to fetch changes up to ac8b8400620a4b0d9ca903ee9ad440bec736f5fa:
mm: unexport follow_pfn (2021-04-08 16:54:38 +0200)
----------------------------------------------------------------
unexport follow_pfn
Follow-up to my pull from last merge window: kvm and vfio lost their
very unsafe use of follow_pfn, this appropriately marks up the very
last user for some userptr-as-buffer use-cases in media. There was
some resistance to outright removing it, maybe we can do this in a few
releases.
----------------------------------------------------------------
Daniel Vetter (3):
mm: Add unsafe_follow_pfn
media/videobuf1|2: Mark follow_pfn usage as unsafe
mm: unexport follow_pfn
drivers/media/common/videobuf2/frame_vector.c | 2 +-
drivers/media/v4l2-core/videobuf-dma-contig.c | 2 +-
include/linux/mm.h | 4 +--
mm/memory.c | 46 +++++++++++++++++----------
mm/nommu.c | 28 ++++++++++++----
security/Kconfig | 13 ++++++++
6 files changed, 68 insertions(+), 27 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2021-05-03 19:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 19:15 Daniel Vetter [this message]
2021-05-03 19:15 ` [PULL] topic/iomem-mmap-vs-gup Daniel Vetter
2021-05-03 19:15 ` Daniel Vetter
2021-05-06 22:30 ` Linus Torvalds
2021-05-06 22:30 ` Linus Torvalds
2021-05-06 22:30 ` Linus Torvalds
2021-05-06 22:30 ` Linus Torvalds
2021-05-07 15:53 ` Daniel Vetter
2021-05-07 15:53 ` Daniel Vetter
2021-05-07 15:53 ` Daniel Vetter
2021-05-08 16:46 ` Linus Torvalds
2021-05-08 16:46 ` Linus Torvalds
2021-05-08 16:46 ` Linus Torvalds
2021-05-08 16:46 ` Linus Torvalds
2021-05-10 7:16 ` Daniel Vetter
2021-05-10 7:16 ` Daniel Vetter
2021-05-10 7:16 ` Daniel Vetter
2021-05-10 7:16 ` Daniel Vetter
2021-05-10 7:29 ` Christoph Hellwig
2021-05-10 7:29 ` Christoph Hellwig
2021-05-17 15:29 ` Daniel Vetter
2021-05-17 15:29 ` Daniel Vetter
2021-05-17 15:29 ` Daniel Vetter
2021-05-17 15:29 ` Daniel Vetter
2021-05-17 22:04 ` Stephen Rothwell
2021-05-17 22:04 ` Stephen Rothwell
2021-05-17 22:04 ` Stephen Rothwell
2021-05-10 13:50 ` Jason Gunthorpe
2021-05-10 13:50 ` Jason Gunthorpe
2021-05-10 13:50 ` Jason Gunthorpe
2021-05-10 14:55 ` Daniel Vetter
2021-05-10 14:55 ` Daniel Vetter
2021-05-10 14:55 ` Daniel Vetter
2021-05-10 14:55 ` Daniel Vetter
2021-05-10 15:34 ` Jason Gunthorpe
2021-05-10 15:34 ` Jason Gunthorpe
2021-05-10 15:34 ` Jason Gunthorpe
2021-05-10 17:57 ` Sean Christopherson
2021-05-10 17:57 ` Sean Christopherson
2021-05-10 17:57 ` Sean Christopherson
2021-05-10 18:13 ` Paolo Bonzini
2021-05-10 18:13 ` Paolo Bonzini
2021-05-10 18:13 ` Paolo Bonzini
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=YJBHiRiCGzojk25U@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-samsung-soc@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.