linux-kernel - Re: [PATCH v2] mm: fix copy_vma() error handling for hugetlb mappings

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: <87frgrc1vi.fsf@igalia.com>
Date: Mon, 26 May 2025 08:38:57 +0200
From: Ricardo Cañuelo Navarro <rcn@...lia.com>
To: "Liam R. Howlett" <Liam.Howlett@...cle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Lorenzo Stoakes
 <lorenzo.stoakes@...cle.com>, Vlastimil Babka <vbabka@...e.cz>, Jann Horn
 <jannh@...gle.com>, Pedro Falcato <pfalcato@...e.de>, revest@...gle.com,
 kernel-dev@...lia.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
 Oscar Salvador <osalvador@...e.de>
Subject: Re: [PATCH v2] mm: fix copy_vma() error handling for hugetlb mappings

Hi Liam, thanks for reviewing:

On Fri, May 23 2025 at 13:45:47, "Liam R. Howlett" <Liam.Howlett@...cle.com> wrote:

> nit: mremap(), do you need the ()? (is it literally this function or the
> call path?)

The mremap call path. This function isn't called directly by mremap()
but it may be called by some of the helper functions in the mremap path,
and I suppose the specific callers are prone to change in the future.

Cheers,
Ricardo