From: Sasha Levin <sashal@kernel.org>
To: Sunil Muthuswamy <sunilmut@microsoft.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH stable v4.19.99]: net: hv_sock: Remove the accept port restriction
Date: Sat, 25 Jan 2020 08:03:55 -0500 [thread overview]
Message-ID: <20200125130355.GJ1706@sasha-vm> (raw)
In-Reply-To: <SN4PR2101MB08801E39B5E814956A4F5708C00E0@SN4PR2101MB0880.namprd21.prod.outlook.com>
On Fri, Jan 24, 2020 at 03:08:18AM +0000, Sunil Muthuswamy wrote:
>commit c742c59e1fbd ("hv_sock: Remove the accept port restriction")
>
>Currently, hv_sock restricts the port the guest socket can accept
>connections on. hv_sock divides the socket port namespace into two parts
>for server side (listening socket), 0-0x7FFFFFFF & 0x80000000-0xFFFFFFFF
>(there are no restrictions on client port namespace). The first part
>(0-0x7FFFFFFF) is reserved for sockets where connections can be accepted.
>The second part (0x80000000-0xFFFFFFFF) is reserved for allocating ports
>for the peer (host) socket, once a connection is accepted.
>This reservation of the port namespace is specific to hv_sock and not
>known by the generic vsock library (ex: af_vsock). This is problematic
>because auto-binds/ephemeral ports are handled by the generic vsock
>library and it has no knowledge of this port reservation and could
>allocate a port that is not compatible with hv_sock (and legitimately so).
>The issue hasn't surfaced so far because the auto-bind code of vsock
>(__vsock_bind_stream) prior to the change 'VSOCK: bind to random port for
>VMADDR_PORT_ANY' would start walking up from LAST_RESERVED_PORT (1023) and
>start assigning ports. That will take a large number of iterations to hit
>0x7FFFFFFF. But, after the above change to randomize port selection, the
>issue has started coming up more frequently.
>There has really been no good reason to have this port reservation logic
>in hv_sock from the get go. Reserving a local port for peer ports is not
>how things are handled generally. Peer ports should reflect the peer port.
>This fixes the issue by lifting the port reservation, and also returns the
>right peer port. Since the code converts the GUID to the peer port (by
>using the first 4 bytes), there is a possibility of conflicts, but that
>seems like a reasonable risk to take, given this is limited to vsock and
>that only applies to all local sockets.
>
>Signed-off-by: Sunil Muthuswamy <sunilmut@microsoft.com>
>Signed-off-by: David S. Miller <davem@davemloft.net>
I'll queue it up when the current release is out in a day or so, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2020-01-25 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 3:08 [PATCH stable v4.19.99]: net: hv_sock: Remove the accept port restriction Sunil Muthuswamy
2020-01-24 9:23 ` Greg KH
2020-01-25 13:03 ` Sasha Levin [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=20200125130355.GJ1706@sasha-vm \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sunilmut@microsoft.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