This attribute is added with the 'created' and 'established' events, but the documentation didn't mention it. The documentation in the UAPI header has been auto-generated by: ./tools/net/ynl/ynl-regen.sh
Unified · Split
| @@ -23,7 +23,8 @@ definitions: · 22 unmodified lines | |||
| 23 | - | 23 | - |
| 24 | name: created | 24 | name: created |
| 25 | doc: | 25 | doc: |
| 26 | token, family, saddr4 | saddr6, daddr4 | daddr6, sport, dport | 26 | token, family, saddr4 | saddr6, daddr4 | daddr6, sport, dport, |
| 27 | server-side | ||
| 27 | A new MPTCP connection has been created. It is the good time to | 28 | A new MPTCP connection has been created. It is the good time to |
| 28 | allocate memory and send ADD_ADDR if needed. Depending on the | 29 | allocate memory and send ADD_ADDR if needed. Depending on the |
| 29 | traffic-patterns it can take a long time until the | 30 | traffic-patterns it can take a long time until the |
| @@ -31,7 +32,8 @@ definitions: · 1 unmodified line | |||
| 31 | - | 32 | - |
| 32 | name: established | 33 | name: established |
| 33 | doc: | 34 | doc: |
| 34 | token, family, saddr4 | saddr6, daddr4 | daddr6, sport, dport | 35 | token, family, saddr4 | saddr6, daddr4 | daddr6, sport, dport, |
| 36 | server-side | ||
| 35 | A MPTCP connection is established (can start new subflows). | 37 | A MPTCP connection is established (can start new subflows). |
| 36 | - | 38 | - |
| 37 | name: closed | 39 | name: closed |
| @@ -13,12 +13,13 @@ · 12 unmodified lines | |||
| 13 | * enum mptcp_event_type | 13 | * enum mptcp_event_type |
| 14 | * @MPTCP_EVENT_UNSPEC: unused event | 14 | * @MPTCP_EVENT_UNSPEC: unused event |
| 15 | * @MPTCP_EVENT_CREATED: token, family, saddr4 | saddr6, daddr4 | daddr6, | 15 | * @MPTCP_EVENT_CREATED: token, family, saddr4 | saddr6, daddr4 | daddr6, |
| 16 | * sport, dport A new MPTCP connection has been created. It is the good time | 16 | * sport, dport, server-side A new MPTCP connection has been created. It is |
| 17 | * to allocate memory and send ADD_ADDR if needed. Depending on the | 17 | * the good time to allocate memory and send ADD_ADDR if needed. Depending on |
| 18 | * traffic-patterns it can take a long time until the MPTCP_EVENT_ESTABLISHED | 18 | * the traffic-patterns it can take a long time until the |
| 19 | * is sent. | 19 | * MPTCP_EVENT_ESTABLISHED is sent. |
| 20 | * @MPTCP_EVENT_ESTABLISHED: token, family, saddr4 | saddr6, daddr4 | daddr6, | 20 | * @MPTCP_EVENT_ESTABLISHED: token, family, saddr4 | saddr6, daddr4 | daddr6, |
| 21 | * sport, dport A MPTCP connection is established (can start new subflows). | 21 | * sport, dport, server-side A MPTCP connection is established (can start new |
| 22 | * subflows). | ||
| 22 | * @MPTCP_EVENT_CLOSED: token A MPTCP connection has stopped. | 23 | * @MPTCP_EVENT_CLOSED: token A MPTCP connection has stopped. |
| 23 | * @MPTCP_EVENT_ANNOUNCED: token, rem_id, family, daddr4 | daddr6 [, dport] A | 24 | * @MPTCP_EVENT_ANNOUNCED: token, rem_id, family, daddr4 | daddr6 [, dport] A |
| 24 | * new address has been announced by the peer. | 25 | * new address has been announced by the peer. |