From: John Hubbard <jhubbard@nvidia.com>
To: <akpm@linux-foundation.org>, <broonie@kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-next@vger.kernel.org>,
<mhocko@suse.cz>, <mm-commits@vger.kernel.org>,
<sfr@canb.auug.org.au>, Daniel Vetter <daniel.vetter@ffwll.ch>,
Jason Gary Gunthorpe <jgg@nvidia.com>
Subject: Re: mmotm 2020-10-06-15-50 uploaded
Date: Wed, 7 Oct 2020 14:03:34 -0700 [thread overview]
Message-ID: <6a97eeaf-781b-f06b-050b-a56c9f8f1632@nvidia.com> (raw)
In-Reply-To: <20201006225133.Y21m5SGLJ%akpm@linux-foundation.org>
On 10/6/20 3:51 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2020-10-06-15-50 has been uploaded to
...
> * mm-frame-vec-drop-gup_flags-from-get_vaddr_frames.patch
> * mm-frame-vec-use-foll_longterm.patch
That last one needs to be dropped--see my note about why in [1].
And syzbot is also complaining [2], correctly, that you can't pass
FOLL_LONGTERM to pin_user_pages_locked().
And the patch right before it, while correct as it stands, should end
up being unnecessary, because Daniel is taking a different approach.
So probably best to drop both of those from mmotm and -next.
[1] https://lore.kernel.org/dri-devel/f5130c7f-eebe-7b21-62b8-68f08212b106@nvidia.com
[2] https://lore.kernel.org/r/000000000000f3c7f005b11111c9@google.com
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2020-10-07 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 22:51 mmotm 2020-10-06-15-50 uploaded akpm
2020-10-07 5:34 ` mmotm 2020-10-06-15-50 uploaded (crypto/asymmetric_keys/public_key*) Randy Dunlap
2020-10-07 21:03 ` John Hubbard [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:
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=6a97eeaf-781b-f06b-050b-a56c9f8f1632@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=jgg@nvidia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).