From: John Hubbard <jhubbard@nvidia.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Jens Axboe <axboe@kernel.dk>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>,
Christoph Hellwig <hch@infradead.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>, Jan Kara <jack@suse.cz>,
Logan Gunthorpe <logang@deltatee.com>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] mm/gup: introduce pin_user_page()
Date: Tue, 30 Aug 2022 17:06:24 -0700 [thread overview]
Message-ID: <b28ba728-f879-7c11-c232-80908bd42853@nvidia.com> (raw)
In-Reply-To: <5aa08b4f-251e-a63d-c36c-324a04ba24f4@redhat.com>
On 8/30/22 05:17, David Hildenbrand wrote:
> (side note: after recent VM_BUG_ON discussions we might want to convert
> the VM_BUG_ON_PAGE in sanity_check_pinned_pages())
Just realized I skipped over this point in my other response.
So, there are 28 "BUG_ON" calls in mm/gup.c, only 3 of which are
BUILD_BUG_ON().
Maybe a single patch that covers all 25 at once is the way to go, I'm
thinking. And of course, any patch that touches any of those lines
should convert to a WARN* variant--whichever lands first.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2022-08-31 0:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 8:36 [PATCH 0/6] convert most filesystems to pin_user_pages_fast() John Hubbard
2022-08-27 8:36 ` [PATCH 1/6] mm/gup: introduce pin_user_page() John Hubbard
2022-08-29 12:07 ` David Hildenbrand
2022-08-29 19:33 ` John Hubbard
2022-08-30 12:17 ` David Hildenbrand
2022-08-30 21:42 ` John Hubbard
2022-08-31 0:06 ` John Hubbard [this message]
2022-08-27 8:36 ` [PATCH 2/6] block: add dio_w_*() wrappers for pin, unpin user pages John Hubbard
2022-08-27 22:27 ` Andrew Morton
2022-08-27 23:59 ` John Hubbard
2022-08-28 0:12 ` Andrew Morton
2022-08-28 0:31 ` John Hubbard
2022-08-28 1:07 ` John Hubbard
2022-08-27 8:36 ` [PATCH 3/6] iov_iter: new iov_iter_pin_pages*() routines John Hubbard
2022-08-27 22:46 ` Al Viro
2022-08-27 22:48 ` John Hubbard
2022-08-27 8:36 ` [PATCH 4/6] block, bio, fs: convert most filesystems to pin_user_pages_fast() John Hubbard
2022-08-27 8:36 ` [PATCH 5/6] NFS: direct-io: convert to FOLL_PIN pages John Hubbard
2022-08-27 22:48 ` Al Viro
2022-08-27 23:55 ` John Hubbard
2022-08-28 0:38 ` Al Viro
2022-08-28 0:39 ` Al Viro
2022-08-28 0:46 ` John Hubbard
2022-08-29 4:59 ` John Hubbard
2022-08-29 16:08 ` Jan Kara
2022-08-29 19:59 ` John Hubbard
2022-08-31 9:43 ` Jan Kara
2022-08-31 18:02 ` John Hubbard
2022-09-01 0:38 ` Al Viro
2022-09-01 9:06 ` Jan Kara
2022-08-27 8:36 ` [PATCH 6/6] fuse: convert direct IO paths to use FOLL_PIN John Hubbard
-- strict thread matches above, loose matches on Subject: below --
2022-02-27 9:34 [PATCH 0/6] block, fs: convert most Direct IO cases to FOLL_PIN jhubbard.send.patches
2022-02-27 9:34 ` [PATCH 1/6] mm/gup: introduce pin_user_page() jhubbard.send.patches
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=b28ba728-f879-7c11-c232-80908bd42853@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=axboe@kernel.dk \
--cc=david@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=miklos@szeredi.hu \
--cc=trond.myklebust@hammerspace.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox