From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <jirislaby@kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>,
<joannelkoong@gmail.com>, <kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PULL] Networking for next-6.1
Date: Tue, 20 Dec 2022 15:28:44 +0900 [thread overview]
Message-ID: <20221220062844.26368-1-kuniyu@amazon.com> (raw)
In-Reply-To: <5bb57ae6-c2a7-e6ea-3fe8-62b8b61bc7c5@kernel.org>
From: Jiri Slaby <jirislaby@kernel.org>
Date: Tue, 20 Dec 2022 07:22:56 +0100
> On 19. 12. 22, 0:25, Kuniyuki Iwashima wrote:
> > From: Jiri Slaby <jirislaby@kernel.org>
> > Date: Fri, 16 Dec 2022 11:49:01 +0100
> >> Hi,
> >>
> >> On 04. 10. 22, 7:20, Jakub Kicinski wrote:
> >>> Joanne Koong (7):
> >>
> >>> net: Add a bhash2 table hashed by port and address
> >>
> >> This makes regression tests of python-ephemeral-port-reserve to fail.
> >>
> >> I'm not sure if the issue is in the commit or in the test.
> >
> > Hi Jiri,
> >
> > Thanks for reporting the issue.
> >
> > It seems we forgot to add TIME_WAIT sockets into bhash2 in
> > inet_twsk_hashdance(), therefore inet_bhash2_conflict() misses
> > TIME_WAIT sockets when validating bind() requests if the address
> > is not a wildcard one.
> >
> > I'll fix it.
>
> Hi,
>
> is there a fix for this available somewhere yet?
Not yet, but I'll CC you when posting a patch.
Thank you.
next prev parent reply other threads:[~2022-12-20 6:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 5:20 [PULL] Networking for next-6.1 Jakub Kicinski
2022-10-04 21:40 ` pr-tracker-bot
2022-12-16 10:49 ` Jiri Slaby
2022-12-18 23:25 ` Kuniyuki Iwashima
2022-12-20 6:22 ` Jiri Slaby
2022-12-20 6:28 ` Kuniyuki Iwashima [this message]
2022-12-21 11:30 ` [PULL] Networking for next-6.1 #forregzbot Thorsten Leemhuis
2022-12-22 12:20 ` Thorsten Leemhuis
2023-01-30 15:19 ` Linux kernel regression tracking (#update)
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=20221220062844.26368-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jirislaby@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).