From: Andi Kleen <ak@linux.intel.com>
To: Carlos Llamas <cmllamas@google.com>
Cc: linux-mm@kvack.org, Mike Kravetz <mike.kravetz@oracle.com>,
Hugh Dickins <hughd@google.com>, Edward Liaw <edliaw@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: Header conflicts with shmget() and SHM_HUGE_2MB
Date: Mon, 3 Jun 2024 12:27:56 -0700 [thread overview]
Message-ID: <Zl4ZPIesxcxI-QE2@tassilo> (raw)
In-Reply-To: <Zl4LC9lTNptB2xTJ@google.com>
> 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
prev parent reply other threads:[~2024-06-03 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 18:27 Header conflicts with shmget() and SHM_HUGE_2MB Carlos Llamas
2024-06-03 19:27 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zl4ZPIesxcxI-QE2@tassilo \
--to=ak@linux.intel.com \
--cc=cmllamas@google.com \
--cc=edliaw@google.com \
--cc=hughd@google.com \
--cc=kernel-team@android.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).