From: DJ Delorie <dj@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v5 2/4] man/man5/tunables.conf: Document system-wide tunables config
Date: Thu, 06 Aug 2026 18:15:15 -0400 [thread overview]
Message-ID: <xnwlu23ngs.fsf@greed.delorie.com> (raw)
In-Reply-To: <anUAwb8lY_u7eU3F@devuan> (message from Alejandro Colomar on Fri, 7 Aug 2026 00:02:47 +0200)
Alejandro Colomar <alx@kernel.org> writes:
> You forgot to sign.
I will never remember that... :-P
>> +The resulting data is read when a new process is created by
>> +.IR ld.so .
>
> Sorry for noticing this in v4; I forgot about it. I see this unresolved
> issue from earlier versions remains.
A program is a file on disk. A process is a running memory image.
Neither fork() nor exec() cause the tunables to be loaded, the process
itself has to do that. For dynamic ELF programs/processes built with
glibc, ld.so does it before it passes control to the ELF image. There
are other types of programs/processes that do not use ld.so and thus do
not read the tunables cache (which is called "ld.so.cache" for a reason ;-)
I don't know how to say this clearly with fewer words...
>> +The syntax allows lines to start with the keyword
>> +.I include
>
> s/I/B/ (since it's a literal, not a variable)
Fixed.
next prev parent reply other threads:[~2026-08-06 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 20:44 [PATCH v5 2/4] man/man5/tunables.conf: Document system-wide tunables config DJ Delorie
2026-08-06 22:02 ` Alejandro Colomar
2026-08-06 22:15 ` DJ Delorie [this message]
2026-08-07 0:06 ` Alejandro Colomar
2026-08-07 0:11 ` Alejandro Colomar
2026-08-07 0:15 ` Alejandro Colomar
2026-08-07 3:25 ` DJ Delorie
2026-08-07 22:36 ` Alejandro Colomar
2026-08-08 3:08 ` DJ Delorie
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=xnwlu23ngs.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
/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