From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: yocto-patches@lists.yoctoproject.org,
Babanpreet Singh <bbnpreetsingh@gmail.com>
Cc: Paul Barker <paul@pbarker.dev>, Mark Hatle <mark.hatle@amd.com>,
Randy MacLeod <randy.macleod@windriver.com>,
Vincent Haupert <mail@vincent-haupert.de>
Subject: Re: [yocto-patches] [pseudo] [PATCH v2 0/2] close_range: implement it rather than return ENOSYS
Date: Thu, 16 Jul 2026 18:08:10 -0500 [thread overview]
Message-ID: <dcda9217-a9be-4451-97d0-d83ddd6dd70f@kernel.crashing.org> (raw)
In-Reply-To: <b6bfa88be0a54a3edf8e55571d4be4e1d54e736e.camel@linuxfoundation.org>
On 7/16/26 5:46 AM, Richard Purdie via lists.yoctoproject.org wrote:
> On Thu, 2026-07-16 at 05:56 +0000, Babanpreet Singh wrote:
>> pseudo's close_range() wrapper has returned ENOSYS unconditionally since
>> 35433e6 ("ports/linux/guts: Add close_range wrapper for glibc 2.34").
>> systemd v260 deleted its /proc/self/fd fallback and treats a failure as
>> fatal, so under pseudo every fork+exec dies. That is [YOCTO #16339]. Full
>> story in v1:
>>
>> https://lore.kernel.org/yocto-patches/20260715054142.7-1-bbnpreetsingh@gmail.com/
>
> I had a quick look through this and it looks ok to me, thanks!
>
>> The v1 question about OP_CLOSEFROM stepping around five of pseudo's
>> descriptors while others exist (pseudo_prefix_dir_fd, pseudo_pwd_lck_fd,
>> pseudo_util_evlog_fd) still stands; happy to send a follow-up if that list
>> is short in both places.
>
> I had a quick look and yes, we should really be protecting these too.
>
> That said, I couldn't see what pseudo_prefix_dir_fd actually helps with
> and I couldn't see why we need that...
This isn't a part of the system I've touched in a very long time. I THOUGHT it
was the fd of the directory PSEUDO_PREFIX, so then when other files (sockets,
etc) needed to be opened, it was all relative to the fd. This allowed the
directory to 'move' if necessary, since we were sure we could still access it
via the 'fd'. (or I'm completely wrong and remembering something different.)
The only 'definitive' reference I can find doesn't explain the why, just the
what doc/program_flow.
I wonder if it was done to hold a file description on the directory so that if
the PSEUDO_PATH was rm'd it wouldn't clear until pseudo itself was unloaded.
--Mark
> Cheers,
>
> Richard
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#4494): https://lists.yoctoproject.org/g/yocto-patches/message/4494
> Mute This Topic: https://lists.yoctoproject.org/mt/120294678/3616948
> Group Owner: yocto-patches+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13201099/3616948/947757854/xyzzy [mark.hatle@kernel.crashing.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
next prev parent reply other threads:[~2026-07-16 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 5:41 [pseudo] [PATCH 0/2] close_range: implement it rather than return ENOSYS Baban
2026-07-15 5:41 ` [pseudo] [PATCH 1/2] ports/linux/guts: Implement close_range() instead of returning ENOSYS Baban
2026-07-15 19:51 ` [yocto-patches] " Paul Barker
2026-07-15 5:41 ` [pseudo] [PATCH 2/2] tests: Add close_range() test Baban
2026-07-15 20:03 ` [yocto-patches] " Paul Barker
2026-07-16 5:56 ` [pseudo] [PATCH v2 0/2] close_range: implement it rather than return ENOSYS Babanpreet Singh
2026-07-16 5:56 ` [pseudo] [PATCH v2 1/2] ports/linux/guts: Implement close_range() instead of returning ENOSYS Babanpreet Singh
2026-07-16 5:56 ` [pseudo] [PATCH v2 2/2] tests: Add close_range() test Babanpreet Singh
2026-07-16 10:46 ` [pseudo] [PATCH v2 0/2] close_range: implement it rather than return ENOSYS Richard Purdie
2026-07-16 15:46 ` Babanpreet Singh
2026-07-16 16:55 ` Richard Purdie
2026-07-16 23:16 ` [yocto-patches] " Mark Hatle
2026-07-16 23:08 ` Mark Hatle [this message]
2026-07-18 4:37 ` [pseudo] [PATCH 0/3] closefrom/close_range: protect every pseudo fd, then drop one Babanpreet Singh
2026-07-18 4:37 ` [pseudo] [PATCH 1/3] pseudo_client: step fully past pseudo's own fds when computing startfd Babanpreet Singh
2026-07-18 4:37 ` [pseudo] [PATCH 2/3] pseudo_client: step around all of pseudo's own fds in closefrom/close_range Babanpreet Singh
2026-07-18 4:37 ` [pseudo] [PATCH 3/3] pseudo_client: remove the unused pseudo_prefix_dir_fd Babanpreet Singh
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=dcda9217-a9be-4451-97d0-d83ddd6dd70f@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=bbnpreetsingh@gmail.com \
--cc=mail@vincent-haupert.de \
--cc=mark.hatle@amd.com \
--cc=paul@pbarker.dev \
--cc=randy.macleod@windriver.com \
--cc=yocto-patches@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.