From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Babanpreet Singh <bbnpreetsingh@gmail.com>,
yocto-patches@lists.yoctoproject.org
Cc: Paul Barker <paul@pbarker.dev>, Mark Hatle <mark.hatle@amd.com>,
Randy MacLeod <randy.macleod@windriver.com>,
Vincent Haupert <mail@vincent-haupert.de>,
Mark Hatle <mark.hatle@kernel.crashing.org>
Subject: Re: [pseudo] [PATCH v2 0/2] close_range: implement it rather than return ENOSYS
Date: Thu, 16 Jul 2026 11:46:46 +0100 [thread overview]
Message-ID: <b6bfa88be0a54a3edf8e55571d4be4e1d54e736e.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260716055633.7-1-bbnpreetsingh@gmail.com>
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...
Cheers,
Richard
next prev parent reply other threads:[~2026-07-16 10:47 UTC|newest]
Thread overview: 11+ 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 ` Richard Purdie [this message]
2026-07-16 15:46 ` [pseudo] [PATCH v2 0/2] close_range: implement it rather than return ENOSYS Babanpreet Singh
2026-07-16 16:55 ` Richard Purdie
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=b6bfa88be0a54a3edf8e55571d4be4e1d54e736e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bbnpreetsingh@gmail.com \
--cc=mail@vincent-haupert.de \
--cc=mark.hatle@amd.com \
--cc=mark.hatle@kernel.crashing.org \
--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.