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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez1duuiePx2pFnTuQK8WEEdKGM4AYCYjDb0XLpJBzNT1=A@mail.gmail.com>
Date: Tue, 8 Apr 2025 20:56:30 +0200
From: Jann Horn <jannh@...gle.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, David Hildenbrand <david@...hat.com>, 
	"Liam R . Howlett" <Liam.Howlett@...cle.com>, Vlastimil Babka <vbabka@...e.cz>, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add memory advice section

On Tue, Apr 8, 2025 at 6:11 PM Lorenzo Stoakes
<lorenzo.stoakes@...cle.com> wrote:
> The madvise code straddles both VMA and page table manipulation. As a
> result, separate it out into its own section and add maintainers/reviewers
> as appropriate.
>
> We additionally include the mman-common.h file as this contains the shared
> madvise flags and it is important we maintain this alongside madvise.c.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>

Acked-by: Jann Horn <jannh@...gle.com>

> +MEMORY MAPPING - MEMORY ADVICE
> +M:     Andrew Morton <akpm@...ux-foundation.org>
> +M:     Liam R. Howlett <Liam.Howlett@...cle.com>
> +M:     Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
> +M:     David Hildenbrand <david@...hat.com>
> +R:     Vlastimil Babka <vbabka@...e.cz>
> +R:     Jann Horn <jannh@...gle.com>
> +S:     Maintained
> +W:     http://www.linux-mm.org
> +T:     git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> +F:     include/uapi/asm-generic/mman-common.h
> +F:     mm/madvise.c

Is it intentional that this one, unlike "MEMORY MAPPING", has no
explicit "L: linux-mm@...ck.org" and relies on the inheritance from
the overall "MEMORY MANAGEMENT" entry for that?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ