linux-kernel - Re: [PATCH] mm: shmem/tmpfs hugepage defaults config choice

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: <20745ea3-4bc5-4032-ae61-b928f2568175@redhat.com>
Date: Mon, 27 Oct 2025 17:26:59 +0100
From: David Hildenbrand <david@...hat.com>
To: Dmitry Ilvokhin <d@...okhin.com>, Matthew Wilcox <willy@...radead.org>
Cc: Michal Hocko <mhocko@...e.com>, Andrew Morton
 <akpm@...ux-foundation.org>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
 "Liam R. Howlett" <Liam.Howlett@...cle.com>, Vlastimil Babka
 <vbabka@...e.cz>, Mike Rapoport <rppt@...nel.org>,
 Suren Baghdasaryan <surenb@...gle.com>, Hugh Dickins <hughd@...gle.com>,
 Baolin Wang <baolin.wang@...ux.alibaba.com>, Kiryl Shutsemau
 <kas@...nel.org>, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
 kernel-team@...a.com
Subject: Re: [PATCH] mm: shmem/tmpfs hugepage defaults config choice

On 27.10.25 17:23, Dmitry Ilvokhin wrote:
> On Fri, Oct 24, 2025 at 09:35:34PM +0100, Matthew Wilcox wrote:
>> On Fri, Oct 24, 2025 at 11:19:50AM +0000, Dmitry Ilvokhin wrote:
>>> Primary motivation for adding config option is to enable policy
>>> enforcement at build time. In large-scale production environments
>>> (Meta's for example), the kernel configuration is often maintained
>>
>> So you work for Meta?  It is poor form to send patches without
>> disclosing your employer.  That way, we'd all be able to see that the
>> positive reviews come from your colleagues rather than having it look
>> like everyone's just "oh, i'm a random developer doing this on my own
>> time".
> 
> Thanks for the feedback, Matthew. For transparency: I work for Meta, and
> this patch is being submitted as part of that work. I know it's common
> for many contributors to submit work-related patches using personal
> emails, but I can understand your point and appreciate the guidance.

Note that Willy, for example, signs-off patches with

	Matthew Wilcox (Oracle) <willy@...radead.org>

-- 
Cheers

David / dhildenb