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: <d59ff240-bb46-47e5-92ad-fd2d9c1a9f42@suse.cz>
Date: Tue, 17 Jun 2025 20:47:07 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: David Hildenbrand <david@...hat.com>,
 Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
 Andrew Morton <akpm@...ux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@...cle.com>,
 Mike Rapoport <rppt@...nel.org>, Suren Baghdasaryan <surenb@...gle.com>,
 Michal Hocko <mhocko@...e.com>, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add further core files to mm core
 section

On 6/16/25 23:10, David Hildenbrand wrote:
> On 16.06.25 22:38, Lorenzo Stoakes wrote:
>> There are a number of files which don't quite belong anywhere else, so
>> place them in the core section. If we determine in future they belong
>> elsewhere we can update incrementally but it is preferable that we assign
>> each file to a section as best we can.
>> 
>> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
>> ---
>> REVIEWERS - let me know if these seem appropriate, I'm eyeballing
>> this. even if they are not quite best placed a 'best effort' is still
>> worthwhile so we establish a place to put all mm files, we can always
>> incrementally update these later.

>> @@ -15764,16 +15760,40 @@ S:	Maintained
>>   W:	http://www.linux-mm.org
>>   T:	git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>>   F:	include/linux/memory.h
>> +F:	include/linux/memremap.h
>>   F:	include/linux/mm.h
>>   F:	include/linux/mm_*.h
>>   F:	include/linux/mmdebug.h
>> +F:	include/linux/mmu_notifier.h
>> +F:	include/linux/mmzone.h
>>   F:	include/linux/pagewalk.h
>>   F:	kernel/fork.c
>>   F:	mm/Kconfig
>>   F:	mm/debug.c
>> +F:	mm/debug_page_ref.c
>> +F:	mm/debug_vm_pgtable.c
> 
> Wondering if there should be a MM DEBUG section. But then, no idea who 
> in their right mind would be willing to maintain that ;)

Guess I'm not in my right mind, but I'd be fine with that. Although most of
my experience is with page_owner and debug_pagealloc which are tied to the
page allocator. And I think it's better when these debug files are in the
section of the functionality they debug. mm/debug_page_ref.c could probably
go to the page allocator. mm/debug_vm_pgtable.c is maybe related to
pagewalk? (it could be redone to a kunit test, btw?). Only mm/debug.c seems
a mix of stuff related to various mm parts... maybe could stay in core then.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ