From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/4] Assorted minor socket creation cleanups
Date: Fri, 12 Jun 2026 01:05:17 +0200 (CEST) [thread overview]
Message-ID: <20260612010516.4d9cfd0e@elisabeth> (raw)
In-Reply-To: <20260609063005.113744-1-david@gibson.dropbear.id.au>
On Tue, 9 Jun 2026 16:30:01 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> As discussed on our recent call, I was looking again at bug 167. I
> discovered it's still fairly fiddly to address this, but while
> investigating spotted a number of cleanups to make in the vicinity. I
> think they make sense even without fixing bug 167 (yet), so here they
> are.
>
> David Gibson (4):
> flow: Correct misleading signature of flowside_sock_l4()
> Makefile: Remove unused DUAL_STACK_SOCKETS define
> fwd, pif: Remove duplicated logic between tcp_listen() and
> udp_listen()
> pif, util: Move listen(2) call from sock_l4_() to pif_listen()
I was about to apply this (there are no apparent conflicts with "[PATCH
0/4] RFC: Improvements to flow specific logging", which I still need to
review), but cppcheck now says:
---
flow.c:216:31: style: inconclusive: Function 'flowside_sock_l4' argument 4 names different: declaration 'tgt' definition 'side'. [funcArgNamesDifferent]
const struct flowside *side)
^
flow.h:176:31: note: Function 'flowside_sock_l4' argument 4 names different: declaration 'tgt' definition 'side'.
const struct flowside *tgt);
^
flow.c:216:31: note: Function 'flowside_sock_l4' argument 4 names different: declaration 'tgt' definition 'side'.
const struct flowside *side)
^
pif.c:111:10: error: Overlapping read/write of union is undefined behavior [overlappingWriteUnion]
ref.fd = sock_l4_dualstack_any(c, ref.type, port, ifname);
^
pif.c:116:10: error: Overlapping read/write of union is undefined behavior [overlappingWriteUnion]
ref.fd = sock_l4(c, ref.type, &sa, ifname);
^
---
...is it just my version (2.19.0)?
--
Stefano
prev parent reply other threads:[~2026-06-11 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 6:30 David Gibson
2026-06-09 6:30 ` [PATCH 1/4] flow: Correct misleading signature of flowside_sock_l4() David Gibson
2026-06-09 6:30 ` [PATCH 2/4] Makefile: Remove unused DUAL_STACK_SOCKETS define David Gibson
2026-06-09 6:30 ` [PATCH 3/4] fwd, pif: Remove duplicated logic between tcp_listen() and udp_listen() David Gibson
2026-06-09 6:30 ` [PATCH 4/4] pif, util: Move listen(2) call from sock_l4_() to pif_listen() David Gibson
2026-06-11 23:05 ` Stefano Brivio [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=20260612010516.4d9cfd0e@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).