Re: sock diag uAPI and MPTCP

2020-06-22 Thread Paolo Abeni
On Sat, 2020-06-20 at 17:44 -0700, David Miller wrote: > From: Paolo Abeni > Date: Fri, 19 Jun 2020 12:54:40 +0200 > > > IPPROTO_MPTCP value (0x106) can't be represented using the current sock > > diag uAPI, as the 'sdiag_protocol' field is 8 bits wide. > > > > To implement diag support for MPTC

Re: sock diag uAPI and MPTCP

2020-06-20 Thread David Miller
From: Paolo Abeni Date: Fri, 19 Jun 2020 12:54:40 +0200 > IPPROTO_MPTCP value (0x106) can't be represented using the current sock > diag uAPI, as the 'sdiag_protocol' field is 8 bits wide. > > To implement diag support for MPTCP socket, we will likely need a > 'inet_diag_req_v3' with a wider 'sd

sock diag uAPI and MPTCP

2020-06-19 Thread Paolo Abeni
Hi, IPPROTO_MPTCP value (0x106) can't be represented using the current sock diag uAPI, as the 'sdiag_protocol' field is 8 bits wide. To implement diag support for MPTCP socket, we will likely need a 'inet_diag_req_v3' with a wider 'sdiag_protocol' field. inet_diag_handler_cmd() could detect the v