From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kuba@kernel.org>, <anjali.rai@intel.com>
Cc: <gregkh@linuxfoundation.org>, <jinen.gandhi@intel.com>,
<joannelkoong@gmail.com>, <kailun.qin@intel.com>,
<kuniyu@amazon.com>, <netdev@vger.kernel.org>,
<regressions@lists.linux.dev>, <stable@vger.kernel.org>
Subject: Re: Regression Issue
Date: Mon, 8 May 2023 12:44:06 -0700 [thread overview]
Message-ID: <20230508194406.73759-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20230508123138.41b5dc48@kernel.org>
From: Jakub Kicinski <kuba@kernel.org>
Date: Mon, 8 May 2023 12:31:38 -0700
> On Mon, 8 May 2023 08:27:49 +0000 Rai, Anjali wrote:
> > On Mon, May 08, 2023 at 07:33:58AM +0000, Rai, Anjali wrote:
> >>> > We have one test which test the functionality of "using the same
> >>> > loopback address and port for both IPV6 and IPV4", The test should
> >>> > result in EADDRINUSE for binding IPv4 to same port, but it was
> >>> > successful
> >>> >
> >>> > Test Description:
> >>> > The test creates sockets for both IPv4 and IPv6, and forces IPV6 to
> >>> > listen for both IPV4 and IPV6 connections; this in turn makes binding
> >>> > another (IPV4) socket on the same port meaningless and results in
> >>> > -EADDRINUSE
> >>> >
> >>> > Our systems had Kernel v6.0.9 and the test was successfully executing, we recently upgraded our systems to v6.2, and we saw this as a failure. The systems which are not upgraded, there it is still passing.
> >>> >
> >>> > We don't exactly at which point this test broke, but our assumption is
> >>> > https://github.com/torvalds/linux/commit/28044fc1d4953b07acec0da4d2fc4
> >>> > 784c57ea6fb
> >>>
> >>> Is there a specific reason you did not add cc: for the authors of that commit?
> >>>
> >>> > Can you please check on your end whether this is an actual regression of a feature request.
> >>>
> >>> If you revert that commit, does it resolve the issue? Have you worked with the Intel networking developers to help debug this further?
>
> > > I am part of Gramine OpenSource Project, I don't know someone from
> > > Intel Networking developers team, if you know someone, please feel
> > > free to add them.
> > >
> > > Building completely linux source code and trying with different
> > > commits, I will not be able to do it today, I can check that may be
> > > tomorrow or day after.
> >
> > The C code was passing earlier, and output was " test completed
> > successfully" but now with v6.2 it is failing and returning
> > "bind(ipv4) was successful even though there is no IPV6_V6ONLY on
> > same port\n"
>
> Adding the mailing list and the experts. Cleaning up the quoting,
> please don't top post going forward.
>
> Kuniyuki, have we seen this before?
Yes, we had the same report [0] and fixed with this patch [1], and it
seems to be backported to v6.1.21 and v6.2.8, not v6.0.y (EOL).
[0]: https://lore.kernel.org/netdev/e21bf153-80b0-9ec0-15ba-e04a4ad42c34@redhat.com/
[1]: https://lore.kernel.org/netdev/20230312031904.4674-2-kuniyu@amazon.com/
[2]: https://lore.kernel.org/stable/?q=tcp%3A+Fix+bind%28%29+conflict+check+for+dual-stack+wildcard+address.
next prev parent reply other threads:[~2023-05-08 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM4PR11MB55183E4B87078E0F496386029A719@DM4PR11MB5518.namprd11.prod.outlook.com>
[not found] ` <2023050851-trapper-preshow-2e4c@gregkh>
[not found] ` <DM4PR11MB55188D8CAB2EBB47E44404359A719@DM4PR11MB5518.namprd11.prod.outlook.com>
[not found] ` <DM4PR11MB5518B5489BB5F01988D22CE99A719@DM4PR11MB5518.namprd11.prod.outlook.com>
2023-05-08 19:31 ` Regression Issue Jakub Kicinski
2023-05-08 19:44 ` Kuniyuki Iwashima [this message]
2023-05-09 5:46 ` Rai, Anjali
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=20230508194406.73759-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=anjali.rai@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jinen.gandhi@intel.com \
--cc=joannelkoong@gmail.com \
--cc=kailun.qin@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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 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).