lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 20 Dec 2017 16:40:13 -0800
From:   Mike Kravetz <>
To:     Andrew Morton <>,
        Michal Hocko <>
Cc:     Marc-André Lureau <>,, open list <>,
        Andrea Arcangeli <>,
        Hugh Dickins <>,,
        David Herrmann <>
Subject: Re: [PATCH v3 0/9] memfd: add sealing to hugetlb-backed memory

On 12/20/2017 04:26 PM, Andrew Morton wrote:
> On Wed, 20 Dec 2017 16:10:51 +0100 Michal Hocko <> wrote:
>> On Wed 20-12-17 15:15:50, Marc-André Lureau wrote:
>>> Hi
>>> On Wed, Nov 15, 2017 at 4:13 AM, Mike Kravetz <> 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:
>>> 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.
> Yup, things are quiet at present.
> I'll suck these up for a bit of testing - please let me know if you'd
> prefer them to be held back for a cycle (ie: for 4.17-rc1)

Thanks Andrew,

As mentioned above there is one issue related to this series that we may
want to address.  It is described in the series at:

I did not get many comments on this series/issue.  If we want to do
something like this, now might be a good time.
Mike Kravetz

Powered by blists - more mailing lists