From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Babanpreet Singh <bbnpreetsingh@gmail.com>,
yocto-patches@lists.yoctoproject.org
Cc: Mark Hatle <mark.hatle@amd.com>,
Mark Hatle <mark.hatle@kernel.crashing.org>,
Paul Barker <paul@pbarker.dev>,
Randy MacLeod <randy.macleod@windriver.com>,
Vincent Haupert <mail@vincent-haupert.de>
Subject: Re: [pseudo] [PATCH 0/3] closefrom/close_range: protect every pseudo fd, then drop one
Date: Tue, 04 Aug 2026 22:13:57 +0100 [thread overview]
Message-ID: <92c180949cc82cbd9025c7673c2ffb8a43896fda.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260730050730.7-1-bbnpreetsingh@gmail.com>
Hi Baban,
On Thu, 2026-07-30 at 05:07 +0000, Babanpreet Singh wrote:
> Yes, that's fine by me, thanks for folding it in and for redoing the
> commit messages. I see the fd-protect patches on master with 1.9.10 on
> top.
>
> I've also read through the close_range respin on master-next. The clamp
> and the OP_CLOSE_RANGE exemption match what I reproduced here.
>
> Sorry the __open64_2 hunt cost you an afternoon. Happy to run the
> close_range probe and the OE reproducer against current master-next and
> report back if another data point would help.
>
> I'll add a note to bug 16339 once the close_range side lands.
We're close, we just need a new version of the patch which makes
close_range and close_from use the same OP call within pseudo. Do you
want to write that or should I?
Cheers,
Richard
next prev parent reply other threads:[~2026-08-04 21:14 UTC|newest]
Thread overview: 33+ 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-28 9:22 ` Richard Purdie
[not found] ` <18C669BEC7E582E7.1643407@lists.yoctoproject.org>
2026-07-28 10:15 ` [yocto-patches] " Richard Purdie
[not found] ` <18C66CA235EABC94.3010641@lists.yoctoproject.org>
2026-07-28 10:48 ` Richard Purdie
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
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
2026-07-28 5:08 ` [pseudo] [PATCH 0/3] closefrom/close_range: protect every pseudo fd, then drop one Babanpreet Singh
2026-07-28 8:14 ` Richard Purdie
[not found] ` <18C6660077364169.3010641@lists.yoctoproject.org>
2026-07-28 15:48 ` [yocto-patches] " Richard Purdie
[not found] ` <18C67ECA93F98D2F.1643407@lists.yoctoproject.org>
2026-07-28 15:59 ` Richard Purdie
2026-07-29 5:08 ` Babanpreet Singh
2026-07-29 6:19 ` Richard Purdie
[not found] ` <18C6AE58128B91FB.3067440@lists.yoctoproject.org>
2026-07-29 8:14 ` [yocto-patches] " Richard Purdie
[not found] ` <18C6B495C3317260.3067440@lists.yoctoproject.org>
2026-07-29 14:55 ` Richard Purdie
2026-07-30 5:07 ` Babanpreet Singh
2026-08-04 21:13 ` Richard Purdie [this message]
2026-08-05 6:22 ` [pseudo] [PATCH v3 0/2] close_range: implement it rather than return ENOSYS Babanpreet Singh
2026-08-05 6:22 ` [pseudo] [PATCH v3 1/2] ports/linux/guts: Implement close_range() instead of returning ENOSYS Babanpreet Singh
2026-08-05 6:22 ` [pseudo] [PATCH v3 2/2] tests: Add close_range() test 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=92c180949cc82cbd9025c7673c2ffb8a43896fda.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.