From: Thomas Butz <btom1990@googlemail.com>
To: wireguard@lists.zx2c4.com
Subject: wireguard-go: potentially faulty GSO detection
Date: Mon, 22 Apr 2024 11:24:25 +0200 (GMT+02:00) [thread overview]
Message-ID: <a1e54eb6-ed75-46c2-9482-93f082635eb3@googlemail.com> (raw)
Both wireguard-go and quic-go currently use the same syscall logic to
check if GSO is available. According to a recent quic-go issue, it's not
enough to check for an error, you also need to check the return value:
https://github.com/quic-go/quic-go/issues/4446
reply other threads:[~2024-11-18 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a1e54eb6-ed75-46c2-9482-93f082635eb3@googlemail.com \
--to=btom1990@googlemail.com \
--cc=wireguard@lists.zx2c4.com \
/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).