linux-kernel - Re: [kernel-hardening] [RFC] memory allocations in genalloc

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2d087abd-1bf4-55aa-ac92-67a9b8f9d177@huawei.com>
Date:   Fri, 18 Aug 2017 17:47:16 +0300
From:   Igor Stoppa <igor.stoppa@...wei.com>
To:     Laura Abbott <labbott@...hat.com>,
        Jes Sorensen <jes@...ined-monkey.org>
CC:     Michal Hocko <mhocko@...nel.org>,
        James Morris <james.l.morris@...cle.com>,
        Jerome Glisse <jglisse@...hat.com>,
        Paul Moore <paul@...l-moore.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>,
        "kernel-hardening@...ts.openwall.com" 
        <kernel-hardening@...ts.openwall.com>,
        <linux-security-module@...r.kernel.org>
Subject: Re: [kernel-hardening] [RFC] memory allocations in genalloc

Hi,

On 18/08/17 16:57, Laura Abbott wrote:
> Again, if you have a specific patch or
> proposal this would be easier to review.


yes, I'm preparing it and will send it out soon,
but it was somehow surprising to me that it was chosen to implement free
with the size parameter.

It made me think that I was overlooking some obvious reason behind the
choice :-S

--
thanks for answering, igor