qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Nicholas Ngai <nicholas@ngai.me>,
	qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH] net/slirp: Use newer slirp_*_hostxfwd API
Date: Sun, 28 Apr 2024 19:23:03 +0200	[thread overview]
Message-ID: <20240428172303.wfmxpslfkjuqucro@begin> (raw)
In-Reply-To: <20240222111726-198aca86-5ac7-4177-a7d7-3aeb1808add1@linutronix.de>

Hello,

Thomas Weißschuh, le jeu. 22 févr. 2024 11:44:13 +0100, a ecrit:
> On Tue, Mar 22, 2022 at 06:58:36PM -0700, Nicholas Ngai wrote:
> > Pinging this. It’s a bit old, though the patch still applies cleanly to
> > master as far as I can tell.
> > 
> > Link to patchew is
> > https://patchew.org/QEMU/20210925214820.18078-1-nicholas@ngai.me/.
> > 
> > I’d love to get https://gitlab.com/qemu-project/qemu/-/issues/347 addressed
> > once libslirp makes a release with added Unix-to-TCP support in the hostxfwd
> > API, but this patch is a requirement for that first.
> 
> I'm also interested in this PATCH and a resolution to issue 347.
> 
> FYI your patch triggers checkpatch warnings, see [0].

Indeed, the code should be fixed to use qemu_strtoi, like already done
elsewhere in net/slirp.c

> Maybe you can resend the patch with the review tags and the checkpatch
> warnings cleaned up.
> 
> Also it would be useful to know how the patch changes the version
> requirements of the libslirp dependency.
> (The version requirement should also be enforced in meson.build)
> Also the commit in subprojects/slirp.wrap should be high enough,
> which seems to already be the case however.
> 
> It seems it requires libslirp 4.6.0 from 2021-06-14, which is only
> available from Debian 12 or Ubuntu 22.04 and no release of RHEL.

The code can easily be made optional with SLIRP_CHECK_VERSION(4,5,0)

(the hostxfwd interface was added in 4.5.0, not 4.6.0 ; the unix socket
part was added in 4.7.0)

Samuel


  reply	other threads:[~2024-04-28 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25 21:48 [PATCH] net/slirp: Use newer slirp_*_hostxfwd API Nicholas Ngai
2021-09-25 23:22 ` Nicholas Ngai
2021-10-05 23:56   ` Samuel Thibault
2022-03-23  1:58     ` Nicholas Ngai
2024-02-22 10:44       ` Thomas Weißschuh
2024-04-28 17:23         ` Samuel Thibault [this message]
2024-04-29  0:14           ` Samuel Thibault
2022-05-02  7:58 ` Breno Leitao

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=20240428172303.wfmxpslfkjuqucro@begin \
    --to=samuel.thibault@gnu.org \
    --cc=jasowang@redhat.com \
    --cc=nicholas@ngai.me \
    --cc=qemu-devel@nongnu.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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 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 NNTP newsgroup(s).