From: Jakub Kicinski <kuba@kernel.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@kernel.org>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org, Paul Holzinger <pholzing@redhat.com>,
Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH v1 net 1/2] tcp: Fix bind() conflict check for dual-stack wildcard address.
Date: Wed, 15 Mar 2023 00:26:25 -0700 [thread overview]
Message-ID: <20230315002625.49bac132@kernel.org> (raw)
In-Reply-To: <533d3c1a-db7e-6ff2-1fdf-fb8bbbb7a14c@leemhuis.info>
On Sun, 12 Mar 2023 12:42:48 +0100 Linux regression tracking (Thorsten
Leemhuis) wrote:
> Link:
> https://lore.kernel.org/netdev/CAG_fn=Ud3zSW7AZWXc+asfMhZVL5ETnvuY44Pmyv4NPv-ijN-A@mail.gmail.com/
> [1]
> Fixes: 5456262d2baa ("net: Fix incorrect address comparison when
> searching for a bind2 bucket")
> Reported-by: Paul Holzinger <pholzing@redhat.com>
> Link:
> https://lore.kernel.org/netdev/e21bf153-80b0-9ec0-15ba-e04a4ad42c34@redhat.com/
> [0]
I tried to fix this manually when applying but:
- your email client wraps your replies
- please don't reply to patches with tags which will look to scripts
and patchwork like tags it should pull into the submission
(Reported-by in particular, here)
next prev parent reply other threads:[~2023-03-15 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 3:19 [PATCH v1 net 0/2] tcp: Fix bind() regression for dual-stack wildcard address Kuniyuki Iwashima
2023-03-12 3:19 ` [PATCH v1 net 1/2] tcp: Fix bind() conflict check " Kuniyuki Iwashima
2023-03-12 11:42 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-15 7:26 ` Jakub Kicinski [this message]
2023-03-15 8:05 ` Thorsten Leemhuis
2023-03-15 19:52 ` Jakub Kicinski
2023-03-13 12:39 ` Eric Dumazet
2023-03-13 16:12 ` Paul Holzinger
2023-03-14 18:34 ` Martin KaFai Lau
2023-03-12 3:19 ` [PATCH v1 net 2/2] selftest: Add test for bind() conflicts Kuniyuki Iwashima
2023-03-15 7:30 ` [PATCH v1 net 0/2] tcp: Fix bind() regression for dual-stack wildcard address 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=20230315002625.49bac132@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pholzing@redhat.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).