From: subashab@codeaurora.org
To: Lorenzo Colitti <lorenzo@google.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: "Maciej Żenczykowski" <zenczykowski@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"Marcelo Ricardo Leitner" <marcelo.leitner@gmail.com>,
"Sean Tranchetti" <stranche@codeaurora.org>,
"Eric Dumazet" <edumazet@google.com>,
"Linux SCTP" <linux-sctp@vger.kernel.org>
Subject: Re: [PATCH v2] net: introduce ip_local_unbindable_ports sysctl
Date: Fri, 13 Dec 2019 01:53:19 +0000 [thread overview]
Message-ID: <2e7ceea704ee71383d3f19d1de63dff4@codeaurora.org> (raw)
In-Reply-To: <CAKD1Yr1V4S3cxvTaBs6pReEZ_3LPobnxdroY+vE3-injHyGt2A@mail.gmail.com>
On 2019-12-12 17:57, Lorenzo Colitti wrote:
> On Fri, Dec 13, 2019 at 9:47 AM Jakub Kicinski
> <jakub.kicinski@netronome.com> wrote:
>> How are the ports which get reserved communicated between the baseband
>> and the AP? Is this part of the standard? Is the driver that talks to
>> the base band in the user space and it knows which ports to reserve
>> statically? Or does the modem dynamically request ports to
>> reserve/inform the host of ports in use?
>
> I'm not an expert in that part of the system, but my understanding is
> that the primary way this is used is to pre-allocate a block of ports
> to be used by the modem on boot, before other applications can bind to
> ports. Subash, do you have more details?
AFAIK these ports are randomly picked and not from a standard.
Userspace gets this information through qrtr during boot.
Atleast in our case, there cannot be any existing user of these ports
since these ports are blocked prior to mobile connection establishment.
We could call SOCK_DIAG_DESTROY on these ports from userspace as a
precaution as applications would gracefully handle the socket errors.
WARNING: multiple messages have this Message-ID (diff)
From: subashab@codeaurora.org
To: Lorenzo Colitti <lorenzo@google.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: "Maciej Żenczykowski" <zenczykowski@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"Marcelo Ricardo Leitner" <marcelo.leitner@gmail.com>,
"Sean Tranchetti" <stranche@codeaurora.org>,
"Eric Dumazet" <edumazet@google.com>,
"Linux SCTP" <linux-sctp@vger.kernel.org>
Subject: Re: [PATCH v2] net: introduce ip_local_unbindable_ports sysctl
Date: Thu, 12 Dec 2019 18:53:19 -0700 [thread overview]
Message-ID: <2e7ceea704ee71383d3f19d1de63dff4@codeaurora.org> (raw)
In-Reply-To: <CAKD1Yr1V4S3cxvTaBs6pReEZ_3LPobnxdroY+vE3-injHyGt2A@mail.gmail.com>
On 2019-12-12 17:57, Lorenzo Colitti wrote:
> On Fri, Dec 13, 2019 at 9:47 AM Jakub Kicinski
> <jakub.kicinski@netronome.com> wrote:
>> How are the ports which get reserved communicated between the baseband
>> and the AP? Is this part of the standard? Is the driver that talks to
>> the base band in the user space and it knows which ports to reserve
>> statically? Or does the modem dynamically request ports to
>> reserve/inform the host of ports in use?
>
> I'm not an expert in that part of the system, but my understanding is
> that the primary way this is used is to pre-allocate a block of ports
> to be used by the modem on boot, before other applications can bind to
> ports. Subash, do you have more details?
AFAIK these ports are randomly picked and not from a standard.
Userspace gets this information through qrtr during boot.
Atleast in our case, there cannot be any existing user of these ports
since these ports are blocked prior to mobile connection establishment.
We could call SOCK_DIAG_DESTROY on these ports from userspace as a
precaution as applications would gracefully handle the socket errors.
next prev parent reply other threads:[~2019-12-13 1:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 0:13 [PATCH] net: introduce ip_local_unbindable_ports sysctl Maciej Żenczykowski
2019-11-27 0:13 ` Maciej Żenczykowski
2019-11-27 2:10 ` subashab
2019-11-27 13:14 ` Marcelo Ricardo Leitner
2019-11-27 13:14 ` Marcelo Ricardo Leitner
2019-11-27 20:50 ` Maciej Żenczykowski
2019-11-27 20:50 ` Maciej Żenczykowski
2019-11-27 22:33 ` David Miller
2019-11-27 22:33 ` David Miller
2019-11-27 23:00 ` Marcelo Ricardo Leitner
2019-11-27 23:00 ` Marcelo Ricardo Leitner
2019-11-29 20:00 ` Maciej Żenczykowski
2019-11-29 20:00 ` Maciej Żenczykowski
2019-12-04 18:27 ` Marcelo Ricardo Leitner
2019-12-04 18:27 ` Marcelo Ricardo Leitner
2019-12-09 22:43 ` Maciej Żenczykowski
2019-12-09 22:43 ` Maciej Żenczykowski
2019-12-09 22:45 ` [PATCH v2] " Maciej Żenczykowski
2019-12-09 22:45 ` Maciej Żenczykowski
2019-12-09 23:42 ` Jakub Kicinski
2019-12-09 23:42 ` Jakub Kicinski
2019-12-10 0:02 ` Maciej Żenczykowski
2019-12-10 0:02 ` Maciej Żenczykowski
2019-12-10 0:18 ` Jakub Kicinski
2019-12-10 0:18 ` Jakub Kicinski
2019-12-10 7:00 ` subashab
2019-12-10 11:46 ` Maciej Żenczykowski
2019-12-10 11:46 ` Maciej Żenczykowski
2019-12-10 17:31 ` Jakub Kicinski
2019-12-10 17:31 ` Jakub Kicinski
2019-12-13 0:16 ` Lorenzo Colitti
2019-12-13 0:16 ` Lorenzo Colitti
2019-12-13 0:47 ` Jakub Kicinski
2019-12-13 0:47 ` Jakub Kicinski
2019-12-13 0:57 ` Lorenzo Colitti
2019-12-13 0:57 ` Lorenzo Colitti
2019-12-13 1:53 ` subashab [this message]
2019-12-13 1:53 ` subashab
2019-12-13 2:04 ` Jakub Kicinski
2019-12-13 2:04 ` Jakub Kicinski
2019-12-10 19:28 ` David Miller
2019-12-10 19:28 ` David Miller
[not found] ` <0101016eee9bf9b5-f5615781-f0a6-41c4-8e9d-ed694eccf07c-000000@us-west-2.amazonses.com>
2019-12-10 17:12 ` Jakub Kicinski
2019-12-10 17:12 ` Jakub Kicinski
2019-12-10 18:12 ` subashab
2019-12-13 0:25 ` [PATCH] " Lorenzo Colitti
2019-12-13 0:25 ` Lorenzo Colitti
2019-12-13 11:49 ` Neil Horman
2019-12-13 11:49 ` Neil Horman
2019-12-19 9:35 ` Lorenzo Colitti
2019-12-19 9:35 ` Lorenzo Colitti
2019-12-19 13:17 ` Neil Horman
2019-12-19 13:17 ` Neil Horman
2019-12-19 14:02 ` Lorenzo Colitti
2019-12-19 14:02 ` Lorenzo Colitti
2019-12-19 16:57 ` Neil Horman
2019-12-19 16:57 ` Neil Horman
2019-12-19 17:52 ` David Miller
2019-12-19 17:52 ` David Miller
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=2e7ceea704ee71383d3f19d1de63dff4@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub.kicinski@netronome.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stranche@codeaurora.org \
--cc=zenczykowski@gmail.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.