From: Oleksii <oleksii.kurochko@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Anthony PERARD" <anthony@xenproject.org>,
"Juergen Gross" <jgross@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Frediano Ziglio" <frediano.ziglio@cloud.com>
Subject: Re: [PATCH for-4.19(?) 0/3] tools/libxs: More CLOEXEC fixes
Date: Mon, 01 Jul 2024 17:06:23 +0200 [thread overview]
Message-ID: <d4bbec5001a49c4032a8418373edb06fd17d1e65.camel@gmail.com> (raw)
In-Reply-To: <20240628143116.1044976-1-andrew.cooper3@citrix.com>
On Fri, 2024-06-28 at 15:31 +0100, Andrew Cooper wrote:
> More fixes to CLOEXEC handling in libxenstore. For 4.19, because the
> first
> attempt to fix this wasn't complete.
>
> libxl is far worse, but I don't have time to get started on that
> mess.
>
> Andrew Cooper (3):
> tools/libxs: Fix CLOEXEC handling in get_dev()
> tools/libxs: Fix CLOEXEC handling in get_socket()
> tools/libxs: Fix CLOEXEC handling in xs_fileno()
>
> tools/config.h.in | 3 ++
> tools/configure | 12 ++++++++
> tools/configure.ac | 2 ++
> tools/libs/store/xs.c | 68 ++++++++++++++++++++++++++++++++++-------
> --
> 4 files changed, 72 insertions(+), 13 deletions(-)
>
For the whole series:
Release-Acked-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>
~ Oleksii
prev parent reply other threads:[~2024-07-01 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 14:31 [PATCH for-4.19(?) 0/3] tools/libxs: More CLOEXEC fixes Andrew Cooper
2024-06-28 14:31 ` [PATCH for-4.19 1/3] tools/libxs: Fix CLOEXEC handling in get_dev() Andrew Cooper
2024-06-28 14:31 ` [PATCH for-4.19 2/3] tools/libxs: Fix CLOEXEC handling in get_socket() Andrew Cooper
2024-06-28 14:31 ` [PATCH for-4.19 3/3] tools/libxs: Fix CLOEXEC handling in xs_fileno() Andrew Cooper
2024-07-01 9:03 ` [PATCH for-4.19(?) 0/3] tools/libxs: More CLOEXEC fixes Jürgen Groß
2024-07-01 9:28 ` Anthony PERARD
2024-07-01 15:06 ` Oleksii [this message]
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=d4bbec5001a49c4032a8418373edb06fd17d1e65.camel@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony@xenproject.org \
--cc=frediano.ziglio@cloud.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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.