public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: linux-man@vger.kernel.org, kernel-team@cloudflare.com,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Simon Horman <simon.horman@corigine.com>
Subject: Re: [PATCH RESEND] ip.7: Document IP_LOCAL_PORT_RANGE socket option
Date: Sat, 8 Jul 2023 19:46:06 +0200	[thread overview]
Message-ID: <5e1bb605-e4c4-4789-7ab1-6e0ff470eeba@gmail.com> (raw)
In-Reply-To: <20230707141739.1171440-1-jakub@cloudflare.com>


[-- Attachment #1.1: Type: text/plain, Size: 2274 bytes --]

Hi Jakub,

On 7/7/23 16:17, Jakub Sitnicki wrote:
> Linux commit 91d0b78c5177 ("inet: Add IP_LOCAL_PORT_RANGE socket option")
> introduced a new socket option available for AF_INET and AF_INET6 sockets.
> 
> Option is available starting from Linux 6.3. Document it.
> 
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
> ---
> Resending the man page update now that the feature has been released.
> Previous submission can be found at [1].
> 
> I'm the author of the feature. We did a technical review of the man page text
> together with the code [2].

Thanks!  Patch applied.

Cheers,
Alex

> 
> [1]: https://lore.kernel.org/all/20230201123634.284689-1-jakub@cloudflare.com/
> [2]: https://lore.kernel.org/all/20221221-sockopt-port-range-v6-0-be255cc0e51f@cloudflare.com/
> ---
>   man7/ip.7 | 21 +++++++++++++++++++++
>   1 file changed, 21 insertions(+)
> 
> diff --git a/man7/ip.7 b/man7/ip.7
> index 92ecf4b3e..c97a917ff 100644
> --- a/man7/ip.7
> +++ b/man7/ip.7
> @@ -499,6 +499,27 @@ and
>   .B IP_TOS
>   are ignored.
>   .TP
> +.BR IP_LOCAL_PORT_RANGE " (since Linux 6.3)"
> +Set or get the per-socket default local port range. This option can be used to
> +clamp down the global local port range, defined by the
> +.I ip_local_port_range
> +.I /proc
> +interface described below, for a given socket.
> +.IP
> +The option takes an
> +.I uint32_t
> +value with the high 16 bits set to the upper range bound, and the low 16 bits
> +set to the lower range bound. Range bounds are inclusive. The 16-bit values
> +should be in host byte order.
> +.IP
> +The lower bound has to be less than the upper bound when both bounds are not
> +zero. Otherwise, setting the option fails with EINVAL.
> +.IP
> +If either bound is outside of the global local port range, or is zero, then that
> +bound has no effect.
> +.IP
> +To reset the setting, pass zero as both the upper and the lower bound.
> +.TP
>   .BR IP_MSFILTER " (since Linux 2.4.22 / 2.5.68)"
>   This option provides access to the advanced full-state filtering API.
>   Argument is an

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-07-08 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 14:17 [PATCH RESEND] ip.7: Document IP_LOCAL_PORT_RANGE socket option Jakub Sitnicki
2023-07-08 17:46 ` Alejandro Colomar [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=5e1bb605-e4c4-4789-7ab1-6e0ff470eeba@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=jakub@cloudflare.com \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=simon.horman@corigine.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