From: Michal Hocko <mhocko@kernel.org>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Hugh Dickins <hughd@google.com>,
nyc@holomorphy.com, Andrew Morton <akpm@linux-foundation.org>,
David Herrmann <dh.herrmann@gmail.com>
Subject: Re: [PATCH v3 0/9] memfd: add sealing to hugetlb-backed memory
Date: Wed, 20 Dec 2017 16:10:51 +0100 [thread overview]
Message-ID: <20171220151051.GV4831@dhcp22.suse.cz> (raw)
In-Reply-To: <CAJ+F1CJCbmUHSMfKou_LP3eMq+p-b7S9vbe1Vv=JsGMFr7bk_w@mail.gmail.com>
On Wed 20-12-17 15:15:50, Marc-André Lureau wrote:
> Hi
>
> On Wed, Nov 15, 2017 at 4:13 AM, Mike Kravetz <mike.kravetz@oracle.com> wrote:
> > +Cc: Andrew, Michal, David
> >
> > Are there any other comments on this patch series from Marc-André? Is anything
> > else needed to move forward?
> >
> > I have reviewed the patches in the series. David Herrmann (the original
> > memfd_create/file sealing author) has also taken a look at the patches.
> >
> > One outstanding issue is sorting out the config option dependencies. Although,
> > IMO this is not a strict requirement for this series. I have addressed this
> > issue in a follow on series:
> > http://lkml.kernel.org/r/20171109014109.21077-1-mike.kravetz@oracle.com
>
> Are we good for the next merge window? Is Hugh Dickins the maintainer
> with the final word, and doing the pull request? (sorry, I am not very
> familiar with kernel development)
Andrew will pick it up, I assume. I will try to get and review this but
there is way too much going on before holiday.
If Mieke feels sufficiently confident about this then I won't object to
the go ahead.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-12-20 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 12:27 [PATCH v3 0/9] memfd: add sealing to hugetlb-backed memory Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 1/9] shmem: unexport shmem_add_seals()/shmem_get_seals() Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 2/9] shmem: rename functions that are memfd-related Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 3/9] hugetlb: expose hugetlbfs_inode_info in header Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 4/9] hugetlb: implement memfd sealing Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 5/9] shmem: add sealing support to hugetlb-backed memfd Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 6/9] memfd-test: test hugetlbfs sealing Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 7/9] memfd-test: add 'memfd-hugetlb:' prefix when testing hugetlbfs Marc-André Lureau
2017-11-07 12:27 ` [PATCH v3 8/9] memfd-test: move common code to a shared unit Marc-André Lureau
2017-11-07 12:28 ` [PATCH v3 9/9] memfd-test: run fuse test on hugetlb backend memory Marc-André Lureau
2017-11-07 21:35 ` Mike Kravetz
2017-11-15 3:13 ` [PATCH v3 0/9] memfd: add sealing to hugetlb-backed memory Mike Kravetz
2017-12-20 14:15 ` Marc-André Lureau
2017-12-20 15:10 ` Michal Hocko [this message]
2017-12-21 0:26 ` Andrew Morton
2017-12-21 0:40 ` Mike Kravetz
2017-12-22 18:30 ` Marc-André Lureau
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=20171220151051.GV4831@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dh.herrmann@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcandre.lureau@gmail.com \
--cc=mike.kravetz@oracle.com \
--cc=nyc@holomorphy.com \
/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).