All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [TEST] nft_tproxy_udp.sh flaky after Fedora 44 upgrade
Date: Thu, 9 Apr 2026 20:28:40 +0200	[thread overview]
Message-ID: <adfv2FGtbge9TCMz@strlen.de> (raw)
In-Reply-To: <add7NeuWubAQzGrg@strlen.de>

Florian Westphal <fw@strlen.de> wrote:
> Jakub Kicinski <kuba@kernel.org> wrote:
> > When you have a sec -- we upgraded the NIPA systems to Fedora 44
> > over the weekend, and nft_tproxy_udp.sh has gotten quite flaky:
> > https://netdev.bots.linux.dev/contest.html?test=nft-tproxy-udp-sh
> > 
> > One thing that we hit immediately is this, in case tproxy test
> > uses socat:
> > 
> > commit e65d8b6f3092398efd7c74e722cb7a516d9a0d6d
> > Date:   Sat Apr 4 16:01:03 2026 -0700
> > 
> >     selftests: drv-net: adjust to socat changes
> >     
> >     socat v1.8.1.0 now defaults to shut-null, it sends an extra
> >     0-length UDP packet when sender disconnects. This breaks
> >     our tests which expect the exact packet sequence.
> >     
> >     Add shut-none which was the old default where necessary.
> 
> Thanks for the pointer, I will try to get to this later today.

No luck so far:

# grep PASS /tmp/log |wc -l
900
# grep -v PASS /tmp/log
# cat /etc/fedora-release
Fedora release 44 (Forty Four)

This on
commit d444044483a98264722ff77ffef407df0589c6c7 (HEAD, nipa/net-next-2026-04-09--06-00)
with a debug build.
(non debug did not trigger anything either).

      reply	other threads:[~2026-04-09 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 22:24 [TEST] nft_tproxy_udp.sh flaky after Fedora 44 upgrade Jakub Kicinski
2026-04-09 10:11 ` Florian Westphal
2026-04-09 18:28   ` Florian Westphal [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=adfv2FGtbge9TCMz@strlen.de \
    --to=fw@strlen.de \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.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.