From: Alejandro Colomar <alx@kernel.org>
To: DJ Delorie <dj@redhat.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v5 2/4] man/man5/tunables.conf: Document system-wide tunables config
Date: Sun, 23 Aug 2026 00:30:04 +0200 [thread overview]
Message-ID: <aooioNNOhTmULlfl@devuan> (raw)
In-Reply-To: <xn8q5y9h3a.fsf@greed.delorie.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
Hi DJ,
> Date: 2026-08-22 13:54:01-0400
> From: DJ Delorie <dj@redhat.com>
>
> Alejandro Colomar <alx@kernel.org> writes:
> > Another detail I noticed now: How is the process name taken?
>
> The kernel doesn't actually tell us the name of the file we're exec'd
> from. It passes an already open file descriptor. So we have to infer
> the file name from /proc/self/exe. If that isn't available, we use
> argv[0] (unless AT_SECURE) but that can be vastly different than
> /proc/self/exe as it's a separate parameter in the execve() call (hence
> unless AT_SECURE ;).
Hmmmm; interesting! I'll push your patch already, as is, and work on
a patch (set) of my own to improve it a little bit. I'll send you the
patch (set) for discussion. Thanks!
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-08-22 22:30 UTC|newest]
Thread overview: 16+ 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
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
2026-08-22 14:10 ` Alejandro Colomar
2026-08-22 17:02 ` DJ Delorie
2026-08-22 17:43 ` Alejandro Colomar
2026-08-22 17:47 ` Alejandro Colomar
2026-08-22 17:54 ` DJ Delorie
2026-08-22 22:30 ` Alejandro Colomar [this message]
2026-08-22 17:52 ` 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=aooioNNOhTmULlfl@devuan \
--to=alx@kernel.org \
--cc=dj@redhat.com \
--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