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: <d2dca02c-ec5a-4b3d-92fe-2b3a3614b5df@redhat.com>
Date: Tue, 23 Sep 2025 10:09:41 +0200
From: David Hildenbrand <david@...hat.com>
To: Ankur Arora <ankur.a.arora@...cle.com>, linux-kernel@...r.kernel.org,
 linux-mm@...ck.org, x86@...nel.org
Cc: akpm@...ux-foundation.org, bp@...en8.de, dave.hansen@...ux.intel.com,
 hpa@...or.com, mingo@...hat.com, mjguzik@...il.com, luto@...nel.org,
 peterz@...radead.org, acme@...nel.org, namhyung@...nel.org,
 tglx@...utronix.de, willy@...radead.org, raghavendra.kt@....com,
 boris.ostrovsky@...cle.com, konrad.wilk@...cle.com
Subject: Re: [PATCH v7 12/16] arm: mm: define clear_user_highpages()

On 17.09.25 17:24, Ankur Arora wrote:
> For configurations with CONFIG_MMU we do not define clear_user_page().
> This runs into issues for configurations with !CONFIG_HIGHMEM, because
> clear_user_highpages() expects to clear_user_page() (via a default
> version of clear_user_pages()).

I'm confused. Can you elaborate once more why we cannot take care of 
that in common code?

If it's about clear_user_pages(), then you can just switch from 
!IS_ENABLED(CONFIG_HIGHMEM) to ifdef in patch #11.

-- 
Cheers

David / dhildenb


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ