From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Matthieu Baerts <matthieu.baerts@tessares.net>,
netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
mathew.j.martineau@linux.intel.com, mptcp@lists.linux.dev
Subject: Re: [PATCH net,v2] uapi: linux: restore IPPROTO_MAX to 256 and add IPPROTO_UAPI_MAX
Date: Thu, 13 Apr 2023 00:22:12 +0200 [thread overview]
Message-ID: <ZDcvFKLZJwdz0Qse@calendula> (raw)
In-Reply-To: <20230412123718.7e6c0b55@kernel.org>
On Wed, Apr 12, 2023 at 12:37:18PM -0700, Jakub Kicinski wrote:
> On Wed, 12 Apr 2023 18:35:40 +0200 Matthieu Baerts wrote:
> > > Is this theoretical, or you think any library might be doing this
> > > already? I lack of sufficient knowledge of the MPTCP ecosystem to
> > > evaluate myself.
> >
> > This is theoretical.
> >
> > But using it with socket's protocol parameter is the only good usage of
> > IPPROTO_MAX for me :-D
>
> Perhaps. No strong preference from me. That said I think I can come up
> with a good name for the SO use: SO_IPPROTO_MAX (which IMHO it's better
> than IPPROTO_UAPI_MAX if Pablo doesn't mind sed'ing?)
SO_ is usually reserved for socket options.
> The name for a max in proto sense... I'm not sure what that would be.
> IPPROTO_MAX_IPPROTO ? IP_IPROTO_MAX ? IP_PROTO_MAX ? Dunno..
next prev parent reply other threads:[~2023-04-12 22:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:25 [PATCH net,v2] uapi: linux: restore IPPROTO_MAX to 256 and add IPPROTO_UAPI_MAX Pablo Neira Ayuso
2023-04-06 10:32 ` uapi: linux: restore IPPROTO_MAX to 256 and add IPPROTO_UAPI_MAX: Tests Results MPTCP CI
2023-04-06 10:45 ` [PATCH net,v2] uapi: linux: restore IPPROTO_MAX to 256 and add IPPROTO_UAPI_MAX Matthieu Baerts
2023-04-12 14:21 ` Jakub Kicinski
2023-04-12 15:22 ` Matthieu Baerts
2023-04-12 16:04 ` Pablo Neira Ayuso
2023-04-12 16:35 ` Matthieu Baerts
2023-04-12 19:37 ` Jakub Kicinski
2023-04-12 22:22 ` Pablo Neira Ayuso [this message]
2023-04-12 16:14 ` Jan Engelhardt
2023-04-12 16:44 ` Matthieu Baerts
2023-04-12 18:24 ` Jan Engelhardt
2023-04-12 14:18 ` Jakub Kicinski
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=ZDcvFKLZJwdz0Qse@calendula \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 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.