linux-kernel - Re: [PATCH v3 0/1] Randomized slab caches for kmalloc()

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>] [day] [month] [year] [list]

Message-ID: <71bd6de4-2cde-54eb-5720-3665d421d8ea@huaweicloud.com>
Date:   Mon, 26 Jun 2023 08:56:40 +0800
From:   "GONG, Ruiqi" <gongruiqi@...weicloud.com>
To:     Markus Elfring <Markus.Elfring@....de>, linux-mm@...ck.org,
        linux-hardening@...r.kernel.org, kernel-janitors@...r.kernel.org
Cc:     LKML <linux-kernel@...r.kernel.org>, cocci@...ia.fr,
        Alexander Lobakin <aleksander.lobakin@...el.com>,
        Alexander Potapenko <glider@...gle.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Christoph Lameter <cl@...ux.com>,
        David Rientjes <rientjes@...gle.com>,
        Dennis Zhou <dennis@...nel.org>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Hyeonggon Yoo <42.hyeyoo@...il.com>,
        James Morris <jmorris@...ei.org>, Jann Horn <jannh@...gle.com>,
        Joonsoo Kim <iamjoonsoo.kim@....com>,
        Kees Cook <keescook@...omium.org>,
        Marco Elver <elver@...gle.com>,
        Paul Moore <paul@...l-moore.com>,
        Pedro Falcato <pedro.falcato@...il.com>,
        Pekka Enberg <penberg@...nel.org>,
        Roman Gushchin <roman.gushchin@...ux.dev>,
        "Serge E . Hallyn" <serge@...lyn.com>, Tejun Heo <tj@...nel.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        Wang Weiyang <wangweiyang2@...wei.com>,
        Xiu Jianfeng <xiujianfeng@...wei.com>
Subject: Re: [PATCH v3 0/1] Randomized slab caches for kmalloc()


On 2023/06/23 16:30, Markus Elfring wrote:
>> I adapted the v2 patch to …
> 
> I suggest to omit the cover letter for a single patch.
> 
> Will any patch series evolve for your proposed changes?
> 

Usually I wouldn't made a cover letter for a single patch, while this
case is an exception because I need a place to hold the additional
explanation about its transformation from RFC patch to formal patch.

> Regards,
> Markus