From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Onyshchuk <oandrew@meta.com>
Subject: Re: [PATCH net] udp: Fix wildcard bind conflict check when using hash2
Date: Fri, 20 Mar 2026 17:59:00 -0700 [thread overview]
Message-ID: <20260320175900.0a7801bb@kernel.org> (raw)
In-Reply-To: <CAAVpQUA2JhaewkprZHccQQu20XgnHmMgZ_q6AZWCP-V+e_YS4A@mail.gmail.com>
On Fri, 20 Mar 2026 16:07:10 -0700 Kuniyuki Iwashima wrote:
> Confirmed this fixes the buggy scenario, thanks !
Should we start a selftest for UDP wildcard bind behavior
or extend bind_wildcard.c or it's odd to ask for it now?
next prev parent reply other threads:[~2026-03-21 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 18:18 [PATCH net] udp: Fix wildcard bind conflict check when using hash2 Martin KaFai Lau
2026-03-20 23:07 ` Kuniyuki Iwashima
2026-03-21 0:59 ` Jakub Kicinski [this message]
2026-03-21 13:44 ` Kuniyuki Iwashima
2026-03-24 2:00 ` patchwork-bot+netdevbpf
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=20260320175900.0a7801bb@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuniyu@google.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oandrew@meta.com \
--cc=pabeni@redhat.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 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.