linux-kernel - Re: Header conflicts with shmget() and SHM_HUGE

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]

Date: Mon, 3 Jun 2024 12:27:56 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Carlos Llamas <cmllamas@...gle.com>
Cc: linux-mm@...ck.org, Mike Kravetz <mike.kravetz@...cle.com>,
	Hugh Dickins <hughd@...gle.com>, Edward Liaw <edliaw@...gle.com>,
	kernel-team@...roid.com, linux-kernel@...r.kernel.org,
	linux-api@...r.kernel.org
Subject: Re: Header conflicts with shmget() and SHM_HUGE_2MB

> I can see such definitions are tagged as "obsolete" in the uapi headers.
> Do we need some ifndef protection with the glibc headers?

They should be still supported, but also the more generic macro.
> 
> What is the advice to follow for userspace? Skip <linux/shm.h> and
> openly redefine the SHM_HUGE_* wherever needed?

glibc (or other C libraries if not using linux/shm) should add the
defines.  Short term you would need to redefine on your own yes.

-Andi