From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Wei Liu <wl@xen.org>
Cc: xen-devel@lists.xenproject.org, Paul Durrant <paul@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jason Andryuk <jandryuk@gmail.com>
Subject: Re: [PATCH v2 00/10] Coverity fixes for vchan-socket-proxy
Date: Fri, 26 Jun 2020 13:12:01 +0200 [thread overview]
Message-ID: <20200626111201.GS1197@mail-itl> (raw)
In-Reply-To: <20200626101807.za6arkdlah7zsjzc@liuwe-devbox-debian-v2>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
On Fri, Jun 26, 2020 at 10:18:07AM +0000, Wei Liu wrote:
> On Wed, Jun 10, 2020 at 11:29:26PM -0400, Jason Andryuk wrote:
> > This series addresses some Coverity reports. To handle closing FDs, a
> > state struct is introduced to track FDs closed in both main() and
> > data_loop().
> >
> > v2 changes "Ensure UNIX path NUL terminated" to avoid a warning with
> > gcc-10. Also, "Move perror() into listen_socket" and "Move perror()
> > into connect_socket" are new.
> >
> > Jason Andryuk (10):
> > vchan-socket-proxy: Ensure UNIX path NUL terminated
> > vchan-socket-proxy: Move perror() into listen_socket
> > vchan-socket-proxy: Move perror() into connect_socket
> > vchan-socket-proxy: Check xs_watch return value
> > vchan-socket-proxy: Unify main return value
> > vchan-socket-proxy: Use a struct to store state
> > vchan-socket-proxy: Switch data_loop() to take state
> > vchan-socket-proxy: Set closed FDs to -1
> > vchan-socket-proxy: Cleanup resources on exit
> > vchan-socket-proxy: Handle closing shared input/output_fd
>
> Acked-by: Wei Liu <wl@xen.org>
>
> Cc Paul. V1 of this series was posted back in May. I consider this
> series bug fixes, so they should be applied for 4.14. The risk is low
> because vchan-socket-proxy is a small utility used by a small number of
> users.
>
> Marek, you gave Review tags in v1. Do they still apply here?
Yes. And also for the new patches 2-3. I thought I've posted it here,
but must have missed clicking "send"...
> >
> > tools/libvchan/vchan-socket-proxy.c | 183 ++++++++++++++++++----------
> > 1 file changed, 119 insertions(+), 64 deletions(-)
> >
> > --
> > 2.25.1
> >
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-26 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 3:29 [PATCH v2 00/10] Coverity fixes for vchan-socket-proxy Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 01/10] vchan-socket-proxy: Ensure UNIX path NUL terminated Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 02/10] vchan-socket-proxy: Move perror() into listen_socket Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 03/10] vchan-socket-proxy: Move perror() into connect_socket Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 04/10] vchan-socket-proxy: Check xs_watch return value Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 05/10] vchan-socket-proxy: Unify main " Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 06/10] vchan-socket-proxy: Use a struct to store state Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 07/10] vchan-socket-proxy: Switch data_loop() to take state Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 08/10] vchan-socket-proxy: Set closed FDs to -1 Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 09/10] vchan-socket-proxy: Cleanup resources on exit Jason Andryuk
2020-06-11 3:29 ` [PATCH v2 10/10] vchan-socket-proxy: Handle closing shared input/output_fd Jason Andryuk
2020-06-26 10:18 ` [PATCH v2 00/10] Coverity fixes for vchan-socket-proxy Wei Liu
2020-06-26 10:41 ` Paul Durrant
2020-06-26 11:12 ` Marek Marczykowski-Górecki [this message]
2020-06-26 11:31 ` Wei Liu
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=20200626111201.GS1197@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jandryuk@gmail.com \
--cc=paul@xen.org \
--cc=wl@xen.org \
--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.