From: Nathan Chancellor <nathan@kernel.org>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "Günther Noack" <gnoack3000@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>, "Kees Cook" <kees@kernel.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org,
"Günther Noack" <gnoack@google.com>,
"Jeff Xu" <jeffxu@chromium.org>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"Paul Moore" <paul@paul-moore.com>,
"Roberto Sassu" <roberto.sassu@huawei.com>,
"Serge Hallyn" <serge@hallyn.com>,
"Stefan Berger" <stefanb@linux.ibm.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v1] selftests: Handle old glibc without execveat(2)
Date: Sun, 19 Jan 2025 12:57:06 -0700 [thread overview]
Message-ID: <20250119195706.GB1824045@ax162> (raw)
In-Reply-To: <20250117.aiy2ooph6Lee@digikod.net>
On Fri, Jan 17, 2025 at 04:47:05PM +0100, Mickaël Salaün wrote:
> On Fri, Jan 17, 2025 at 03:42:22PM +0100, Günther Noack wrote:
> > Do you want to add a comment next to these, to remind ourselves do undo this?
> > You are surely not planning to support old versions of glibc indefinitely?
>
> I don't about glibc. Minimal versions for other tools are documented
> here though:
> https://docs.kernel.org/process/changes.html
>
> Nathan, Jon, any idea?
I do not know if the idea of setting a minimum supported version of a
libc has ever come up before (at least I am unaware of one). I suspect
most people do a patch like this then move on because it is the
maximally compatible option and these samples are not changing much, are
they? This is the first build error I can recall seeing as a result of
using an older glibc environment. If we would like to seriously consider
setting a minimum supported version of glibc, it deserves a conversation
with a wider audience since it could impact areas other than the
samples, such as host tools (and IMHO, feels like a big hammer).
Cheers,
Nathan
next prev parent reply other threads:[~2025-01-19 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 14:47 [PATCH v1] selftests: Handle old glibc without execveat(2) Mickaël Salaün
2025-01-17 14:42 ` Günther Noack
2025-01-17 15:47 ` Mickaël Salaün
2025-01-19 19:57 ` Nathan Chancellor [this message]
2025-01-27 19:39 ` Kees Cook
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=20250119195706.GB1824045@ax162 \
--to=nathan@kernel.org \
--cc=corbet@lwn.net \
--cc=gnoack3000@gmail.com \
--cc=gnoack@google.com \
--cc=jeffxu@chromium.org \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=sfr@canb.auug.org.au \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.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).