2021-11-01 00:00:02 +08:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0+ */
|
|
|
|
/*
|
|
|
|
* Copyright (c) 2021 Taehee Yoo <ap420073@gmail.com>
|
|
|
|
*/
|
|
|
|
#ifndef _NET_AMT_H_
|
|
|
|
#define _NET_AMT_H_
|
|
|
|
|
|
|
|
#include <linux/siphash.h>
|
|
|
|
#include <linux/jhash.h>
|
2022-07-21 07:57:58 +08:00
|
|
|
#include <linux/netdevice.h>
|
|
|
|
#include <net/gro_cells.h>
|
|
|
|
#include <net/rtnetlink.h>
|
2021-11-01 00:00:02 +08:00
|
|
|
|
|
|
|
enum amt_msg_type {
|
|
|
|
AMT_MSG_DISCOVERY = 1,
|
|
|
|
AMT_MSG_ADVERTISEMENT,
|
|
|
|
AMT_MSG_REQUEST,
|
|
|
|
AMT_MSG_MEMBERSHIP_QUERY,
|
|
|
|
AMT_MSG_MEMBERSHIP_UPDATE,
|
|
|
|
AMT_MSG_MULTICAST_DATA,
|
2022-05-24 00:17:06 +08:00
|
|
|
AMT_MSG_TEARDOWN,
|
2021-11-01 00:00:02 +08:00
|
|
|
__AMT_MSG_MAX,
|
|
|
|
};
|
|
|
|
|
|
|
|
#define AMT_MSG_MAX (__AMT_MSG_MAX - 1)
|
|
|
|
|
2021-11-01 00:00:04 +08:00
|
|
|
enum amt_ops {
|
|
|
|
/* A*B */
|
|
|
|
AMT_OPS_INT,
|
|
|
|
/* A+B */
|
|
|
|
AMT_OPS_UNI,
|
|
|
|
/* A-B */
|
|
|
|
AMT_OPS_SUB,
|
|
|
|
/* B-A */
|
|
|
|
AMT_OPS_SUB_REV,
|
|
|
|
__AMT_OPS_MAX,
|
|
|
|
};
|
|
|
|
|
|
|
|
#define AMT_OPS_MAX (__AMT_OPS_MAX - 1)
|
|
|
|
|
|
|
|
enum amt_filter {
|
|
|
|
AMT_FILTER_FWD,
|
|
|
|
AMT_FILTER_D_FWD,
|
|
|
|
AMT_FILTER_FWD_NEW,
|
|
|
|
AMT_FILTER_D_FWD_NEW,
|
|
|
|
AMT_FILTER_ALL,
|
|
|
|
AMT_FILTER_NONE_NEW,
|
|
|
|
AMT_FILTER_BOTH,
|
|
|
|
AMT_FILTER_BOTH_NEW,
|
|
|
|
__AMT_FILTER_MAX,
|
|
|
|
};
|
|
|
|
|
|
|
|
#define AMT_FILTER_MAX (__AMT_FILTER_MAX - 1)
|
|
|
|
|
|
|
|
enum amt_act {
|
|
|
|
AMT_ACT_GMI,
|
|
|
|
AMT_ACT_GMI_ZERO,
|
|
|
|
AMT_ACT_GT,
|
|
|
|
AMT_ACT_STATUS_FWD_NEW,
|
|
|
|
AMT_ACT_STATUS_D_FWD_NEW,
|
|
|
|
AMT_ACT_STATUS_NONE_NEW,
|
|
|
|
__AMT_ACT_MAX,
|
|
|
|
};
|
|
|
|
|
|
|
|
#define AMT_ACT_MAX (__AMT_ACT_MAX - 1)
|
|
|
|
|
2021-11-01 00:00:02 +08:00
|
|
|
enum amt_status {
|
|
|
|
AMT_STATUS_INIT,
|
|
|
|
AMT_STATUS_SENT_DISCOVERY,
|
|
|
|
AMT_STATUS_RECEIVED_DISCOVERY,
|
|
|
|
AMT_STATUS_SENT_ADVERTISEMENT,
|
|
|
|
AMT_STATUS_RECEIVED_ADVERTISEMENT,
|
|
|
|
AMT_STATUS_SENT_REQUEST,
|
|
|
|
AMT_STATUS_RECEIVED_REQUEST,
|
|
|
|
AMT_STATUS_SENT_QUERY,
|
|
|
|
AMT_STATUS_RECEIVED_QUERY,
|
|
|
|
AMT_STATUS_SENT_UPDATE,
|
|
|
|
AMT_STATUS_RECEIVED_UPDATE,
|
|
|
|
__AMT_STATUS_MAX,
|
|
|
|
};
|
|
|
|
|
|
|
|
#define AMT_STATUS_MAX (__AMT_STATUS_MAX - 1)
|
|
|
|
|
amt: use workqueue for gateway side message handling
There are some synchronization issues(amt->status, amt->req_cnt, etc)
if the interface is in gateway mode because gateway message handlers
are processed concurrently.
This applies a work queue for processing these messages instead of
expanding the locking context.
So, the purposes of this patch are to fix exist race conditions and to make
gateway to be able to validate a gateway status more correctly.
When the AMT gateway interface is created, it tries to establish to relay.
The establishment step looks stateless, but it should be managed well.
In order to handle messages in the gateway, it saves the current
status(i.e. AMT_STATUS_XXX).
This patch makes gateway code to be worked with a single thread.
Now, all messages except the multicast are triggered(received or
delay expired), and these messages will be stored in the event
queue(amt->events).
Then, the single worker processes stored messages asynchronously one
by one.
The multicast data message type will be still processed immediately.
Now, amt->lock is only needed to access the event queue(amt->events)
if an interface is the gateway mode.
Fixes: cbc21dc1cfe9 ("amt: add data plane of amt interface")
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
2022-07-18 00:09:03 +08:00
|
|
|
/* Gateway events only */
|
|
|
|
enum amt_event {
|
|
|
|
AMT_EVENT_NONE,
|
|
|
|
AMT_EVENT_RECEIVE,
|
|
|
|
AMT_EVENT_SEND_DISCOVERY,
|
|
|
|
AMT_EVENT_SEND_REQUEST,
|
|
|
|
__AMT_EVENT_MAX,
|
|
|
|
};
|
|
|
|
|
amt: add data plane of amt interface
Before forwarding multicast traffic, the amt interface establishes between
gateway and relay. In order to establish, amt defined some message type
and those message flow looks like the below.
Gateway Relay
------- -----
: Request :
[1] | N |
|---------------------->|
| Membership Query | [2]
| N,MAC,gADDR,gPORT |
|<======================|
[3] | Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR,gPORT |<-----------------() |
| *IP Packet(S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
~ ~
~ Request ~
[4] | N' |
|---------------------->|
| Membership Query | [5]
| N',MAC',gADDR',gPORT' |
|<======================|
[6] | |
| Teardown |
| N,MAC,gADDR,gPORT |
|---------------------->|
| | [7]
| Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR',gPORT' |<-----------------() |
| *IP Packet (S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
| |
: :
1. Discovery
- Sent by Gateway to Relay
- To find Relay unique ip address
2. Advertisement
- Sent by Relay to Gateway
- Contains the unique IP address
3. Request
- Sent by Gateway to Relay
- Solicit to receive 'Query' message.
4. Query
- Sent by Relay to Gateway
- Contains General Query message.
5. Update
- Sent by Gateway to Relay
- Contains report message.
6. Multicast Data
- Sent by Relay to Gateway
- encapsulated multicast traffic.
7. Teardown
- Not supported at this time.
Except for the Teardown message, it supports all messages.
In the next patch, IGMP/MLD logic will be added.
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-11-01 00:00:03 +08:00
|
|
|
struct amt_header {
|
|
|
|
#if defined(__LITTLE_ENDIAN_BITFIELD)
|
|
|
|
u8 type:4,
|
|
|
|
version:4;
|
|
|
|
#elif defined(__BIG_ENDIAN_BITFIELD)
|
|
|
|
u8 version:4,
|
|
|
|
type:4;
|
|
|
|
#else
|
|
|
|
#error "Please fix <asm/byteorder.h>"
|
|
|
|
#endif
|
|
|
|
} __packed;
|
|
|
|
|
2021-11-01 00:00:02 +08:00
|
|
|
struct amt_header_discovery {
|
|
|
|
#if defined(__LITTLE_ENDIAN_BITFIELD)
|
|
|
|
u32 type:4,
|
|
|
|
version:4,
|
|
|
|
reserved:24;
|
|
|
|
#elif defined(__BIG_ENDIAN_BITFIELD)
|
|
|
|
u32 version:4,
|
|
|
|
type:4,
|
|
|
|
reserved:24;
|
|
|
|
#else
|
|
|
|
#error "Please fix <asm/byteorder.h>"
|
|
|
|
#endif
|
|
|
|
__be32 nonce;
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct amt_header_advertisement {
|
|
|
|
#if defined(__LITTLE_ENDIAN_BITFIELD)
|
|
|
|
u32 type:4,
|
|
|
|
version:4,
|
|
|
|
reserved:24;
|
|
|
|
#elif defined(__BIG_ENDIAN_BITFIELD)
|
|
|
|
u32 version:4,
|
|
|
|
type:4,
|
|
|
|
reserved:24;
|
|
|
|
#else
|
|
|
|
#error "Please fix <asm/byteorder.h>"
|
|
|
|
#endif
|
|
|
|
__be32 nonce;
|
|
|
|
__be32 ip4;
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct amt_header_request {
|
|
|
|
#if defined(__LITTLE_ENDIAN_BITFIELD)
|
|
|
|
u32 type:4,
|
|
|
|
version:4,
|
|
|
|
reserved1:7,
|
|
|
|
p:1,
|
|
|
|
reserved2:16;
|
|
|
|
#elif defined(__BIG_ENDIAN_BITFIELD)
|
|
|
|
u32 version:4,
|
|
|
|
type:4,
|
|
|
|
p:1,
|
|
|
|
reserved1:7,
|
|
|
|
reserved2:16;
|
|
|
|
#else
|
|
|
|
#error "Please fix <asm/byteorder.h>"
|
|
|
|
#endif
|
|
|
|
__be32 nonce;
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct amt_header_membership_query {
|
|
|
|
#if defined(__LITTLE_ENDIAN_BITFIELD)
|
|
|
|
u64 type:4,
|
|
|
|
version:4,
|
|
|
|
reserved:6,
|
|
|
|
l:1,
|
|
|
|
g:1,
|
|
|
|
response_mac:48;
|
|
|
|
#elif defined(__BIG_ENDIAN_BITFIELD)
|
|
|
|
u64 version:4,
|
|
|
|
type:4,
|
|
|
|
g:1,
|
|
|
|
l:1,
|
|
|
|
reserved:6,
|
|
|
|
response_mac:48;
|
|
|
|
#else
|
|
|
|
#error "Please fix <asm/byteorder.h>"
|
|
|
|
#endif
|
|
|
|
__be32 nonce;
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct amt_header_membership_update {
|
|
|
|
#if defined(__LITTLE_ENDIAN_BITFIELD)
|
|
|
|
u64 type:4,
|
|
|
|
version:4,
|
|
|
|
reserved:8,
|
|
|
|
response_mac:48;
|
|
|
|
#elif defined(__BIG_ENDIAN_BITFIELD)
|
|
|
|
u64 version:4,
|
|
|
|
type:4,
|
|
|
|
reserved:8,
|
|
|
|
response_mac:48;
|
|
|
|
#else
|
|
|
|
#error "Please fix <asm/byteorder.h>"
|
|
|
|
#endif
|
|
|
|
__be32 nonce;
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct amt_header_mcast_data {
|
|
|
|
#if defined(__LITTLE_ENDIAN_BITFIELD)
|
|
|
|
u16 type:4,
|
|
|
|
version:4,
|
|
|
|
reserved:8;
|
|
|
|
#elif defined(__BIG_ENDIAN_BITFIELD)
|
|
|
|
u16 version:4,
|
|
|
|
type:4,
|
|
|
|
reserved:8;
|
|
|
|
#else
|
|
|
|
#error "Please fix <asm/byteorder.h>"
|
|
|
|
#endif
|
|
|
|
} __packed;
|
|
|
|
|
2021-11-01 00:00:04 +08:00
|
|
|
struct amt_headers {
|
|
|
|
union {
|
|
|
|
struct amt_header_discovery discovery;
|
|
|
|
struct amt_header_advertisement advertisement;
|
|
|
|
struct amt_header_request request;
|
|
|
|
struct amt_header_membership_query query;
|
|
|
|
struct amt_header_membership_update update;
|
|
|
|
struct amt_header_mcast_data data;
|
|
|
|
};
|
|
|
|
} __packed;
|
|
|
|
|
2021-11-01 00:00:02 +08:00
|
|
|
struct amt_gw_headers {
|
|
|
|
union {
|
|
|
|
struct amt_header_discovery discovery;
|
|
|
|
struct amt_header_request request;
|
|
|
|
struct amt_header_membership_update update;
|
|
|
|
};
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct amt_relay_headers {
|
|
|
|
union {
|
|
|
|
struct amt_header_advertisement advertisement;
|
|
|
|
struct amt_header_membership_query query;
|
|
|
|
struct amt_header_mcast_data data;
|
|
|
|
};
|
|
|
|
} __packed;
|
|
|
|
|
amt: add data plane of amt interface
Before forwarding multicast traffic, the amt interface establishes between
gateway and relay. In order to establish, amt defined some message type
and those message flow looks like the below.
Gateway Relay
------- -----
: Request :
[1] | N |
|---------------------->|
| Membership Query | [2]
| N,MAC,gADDR,gPORT |
|<======================|
[3] | Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR,gPORT |<-----------------() |
| *IP Packet(S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
~ ~
~ Request ~
[4] | N' |
|---------------------->|
| Membership Query | [5]
| N',MAC',gADDR',gPORT' |
|<======================|
[6] | |
| Teardown |
| N,MAC,gADDR,gPORT |
|---------------------->|
| | [7]
| Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR',gPORT' |<-----------------() |
| *IP Packet (S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
| |
: :
1. Discovery
- Sent by Gateway to Relay
- To find Relay unique ip address
2. Advertisement
- Sent by Relay to Gateway
- Contains the unique IP address
3. Request
- Sent by Gateway to Relay
- Solicit to receive 'Query' message.
4. Query
- Sent by Relay to Gateway
- Contains General Query message.
5. Update
- Sent by Gateway to Relay
- Contains report message.
6. Multicast Data
- Sent by Relay to Gateway
- encapsulated multicast traffic.
7. Teardown
- Not supported at this time.
Except for the Teardown message, it supports all messages.
In the next patch, IGMP/MLD logic will be added.
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-11-01 00:00:03 +08:00
|
|
|
struct amt_skb_cb {
|
|
|
|
struct amt_tunnel_list *tunnel;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct amt_tunnel_list {
|
|
|
|
struct list_head list;
|
|
|
|
/* Protect All resources under an amt_tunne_list */
|
|
|
|
spinlock_t lock;
|
|
|
|
struct amt_dev *amt;
|
|
|
|
u32 nr_groups;
|
|
|
|
u32 nr_sources;
|
|
|
|
enum amt_status status;
|
|
|
|
struct delayed_work gc_wq;
|
|
|
|
__be16 source_port;
|
|
|
|
__be32 ip4;
|
|
|
|
__be32 nonce;
|
|
|
|
siphash_key_t key;
|
|
|
|
u64 mac:48,
|
|
|
|
reserved:16;
|
|
|
|
struct rcu_head rcu;
|
|
|
|
struct hlist_head groups[];
|
|
|
|
};
|
|
|
|
|
2021-11-01 00:00:04 +08:00
|
|
|
union amt_addr {
|
|
|
|
__be32 ip4;
|
|
|
|
#if IS_ENABLED(CONFIG_IPV6)
|
|
|
|
struct in6_addr ip6;
|
|
|
|
#endif
|
|
|
|
};
|
|
|
|
|
|
|
|
/* RFC 3810
|
|
|
|
*
|
|
|
|
* When the router is in EXCLUDE mode, the router state is represented
|
|
|
|
* by the notation EXCLUDE (X,Y), where X is called the "Requested List"
|
|
|
|
* and Y is called the "Exclude List". All sources, except those from
|
|
|
|
* the Exclude List, will be forwarded by the router
|
|
|
|
*/
|
|
|
|
enum amt_source_status {
|
|
|
|
AMT_SOURCE_STATUS_NONE,
|
|
|
|
/* Node of Requested List */
|
|
|
|
AMT_SOURCE_STATUS_FWD,
|
|
|
|
/* Node of Exclude List */
|
|
|
|
AMT_SOURCE_STATUS_D_FWD,
|
|
|
|
};
|
|
|
|
|
|
|
|
/* protected by gnode->lock */
|
|
|
|
struct amt_source_node {
|
|
|
|
struct hlist_node node;
|
|
|
|
struct amt_group_node *gnode;
|
|
|
|
struct delayed_work source_timer;
|
|
|
|
union amt_addr source_addr;
|
|
|
|
enum amt_source_status status;
|
|
|
|
#define AMT_SOURCE_OLD 0
|
|
|
|
#define AMT_SOURCE_NEW 1
|
|
|
|
u8 flags;
|
|
|
|
struct rcu_head rcu;
|
|
|
|
};
|
|
|
|
|
|
|
|
/* Protected by amt_tunnel_list->lock */
|
|
|
|
struct amt_group_node {
|
|
|
|
struct amt_dev *amt;
|
|
|
|
union amt_addr group_addr;
|
|
|
|
union amt_addr host_addr;
|
|
|
|
bool v6;
|
|
|
|
u8 filter_mode;
|
|
|
|
u32 nr_sources;
|
|
|
|
struct amt_tunnel_list *tunnel_list;
|
|
|
|
struct hlist_node node;
|
|
|
|
struct delayed_work group_timer;
|
|
|
|
struct rcu_head rcu;
|
|
|
|
struct hlist_head sources[];
|
|
|
|
};
|
|
|
|
|
amt: use workqueue for gateway side message handling
There are some synchronization issues(amt->status, amt->req_cnt, etc)
if the interface is in gateway mode because gateway message handlers
are processed concurrently.
This applies a work queue for processing these messages instead of
expanding the locking context.
So, the purposes of this patch are to fix exist race conditions and to make
gateway to be able to validate a gateway status more correctly.
When the AMT gateway interface is created, it tries to establish to relay.
The establishment step looks stateless, but it should be managed well.
In order to handle messages in the gateway, it saves the current
status(i.e. AMT_STATUS_XXX).
This patch makes gateway code to be worked with a single thread.
Now, all messages except the multicast are triggered(received or
delay expired), and these messages will be stored in the event
queue(amt->events).
Then, the single worker processes stored messages asynchronously one
by one.
The multicast data message type will be still processed immediately.
Now, amt->lock is only needed to access the event queue(amt->events)
if an interface is the gateway mode.
Fixes: cbc21dc1cfe9 ("amt: add data plane of amt interface")
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
2022-07-18 00:09:03 +08:00
|
|
|
#define AMT_MAX_EVENTS 16
|
|
|
|
struct amt_events {
|
|
|
|
enum amt_event event;
|
|
|
|
struct sk_buff *skb;
|
|
|
|
};
|
|
|
|
|
2021-11-01 00:00:02 +08:00
|
|
|
struct amt_dev {
|
|
|
|
struct net_device *dev;
|
|
|
|
struct net_device *stream_dev;
|
|
|
|
struct net *net;
|
|
|
|
/* Global lock for amt device */
|
|
|
|
spinlock_t lock;
|
|
|
|
/* Used only in relay mode */
|
|
|
|
struct list_head tunnel_list;
|
|
|
|
struct gro_cells gro_cells;
|
|
|
|
|
|
|
|
/* Protected by RTNL */
|
|
|
|
struct delayed_work discovery_wq;
|
|
|
|
/* Protected by RTNL */
|
|
|
|
struct delayed_work req_wq;
|
|
|
|
/* Protected by RTNL */
|
|
|
|
struct delayed_work secret_wq;
|
amt: use workqueue for gateway side message handling
There are some synchronization issues(amt->status, amt->req_cnt, etc)
if the interface is in gateway mode because gateway message handlers
are processed concurrently.
This applies a work queue for processing these messages instead of
expanding the locking context.
So, the purposes of this patch are to fix exist race conditions and to make
gateway to be able to validate a gateway status more correctly.
When the AMT gateway interface is created, it tries to establish to relay.
The establishment step looks stateless, but it should be managed well.
In order to handle messages in the gateway, it saves the current
status(i.e. AMT_STATUS_XXX).
This patch makes gateway code to be worked with a single thread.
Now, all messages except the multicast are triggered(received or
delay expired), and these messages will be stored in the event
queue(amt->events).
Then, the single worker processes stored messages asynchronously one
by one.
The multicast data message type will be still processed immediately.
Now, amt->lock is only needed to access the event queue(amt->events)
if an interface is the gateway mode.
Fixes: cbc21dc1cfe9 ("amt: add data plane of amt interface")
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
2022-07-18 00:09:03 +08:00
|
|
|
struct work_struct event_wq;
|
2021-11-01 00:00:02 +08:00
|
|
|
/* AMT status */
|
|
|
|
enum amt_status status;
|
|
|
|
/* Generated key */
|
|
|
|
siphash_key_t key;
|
|
|
|
struct socket __rcu *sock;
|
|
|
|
u32 max_groups;
|
|
|
|
u32 max_sources;
|
|
|
|
u32 hash_buckets;
|
|
|
|
u32 hash_seed;
|
|
|
|
/* Default 128 */
|
|
|
|
u32 max_tunnels;
|
|
|
|
/* Default 128 */
|
|
|
|
u32 nr_tunnels;
|
|
|
|
/* Gateway or Relay mode */
|
|
|
|
u32 mode;
|
|
|
|
/* Default 2268 */
|
|
|
|
__be16 relay_port;
|
|
|
|
/* Default 2268 */
|
|
|
|
__be16 gw_port;
|
|
|
|
/* Outer local ip */
|
|
|
|
__be32 local_ip;
|
|
|
|
/* Outer remote ip */
|
|
|
|
__be32 remote_ip;
|
|
|
|
/* Outer discovery ip */
|
|
|
|
__be32 discovery_ip;
|
|
|
|
/* Only used in gateway mode */
|
|
|
|
__be32 nonce;
|
|
|
|
/* Gateway sent request and received query */
|
|
|
|
bool ready4;
|
|
|
|
bool ready6;
|
|
|
|
u8 req_cnt;
|
|
|
|
u8 qi;
|
|
|
|
u64 qrv;
|
|
|
|
u64 qri;
|
|
|
|
/* Used only in gateway mode */
|
|
|
|
u64 mac:48,
|
|
|
|
reserved:16;
|
amt: use workqueue for gateway side message handling
There are some synchronization issues(amt->status, amt->req_cnt, etc)
if the interface is in gateway mode because gateway message handlers
are processed concurrently.
This applies a work queue for processing these messages instead of
expanding the locking context.
So, the purposes of this patch are to fix exist race conditions and to make
gateway to be able to validate a gateway status more correctly.
When the AMT gateway interface is created, it tries to establish to relay.
The establishment step looks stateless, but it should be managed well.
In order to handle messages in the gateway, it saves the current
status(i.e. AMT_STATUS_XXX).
This patch makes gateway code to be worked with a single thread.
Now, all messages except the multicast are triggered(received or
delay expired), and these messages will be stored in the event
queue(amt->events).
Then, the single worker processes stored messages asynchronously one
by one.
The multicast data message type will be still processed immediately.
Now, amt->lock is only needed to access the event queue(amt->events)
if an interface is the gateway mode.
Fixes: cbc21dc1cfe9 ("amt: add data plane of amt interface")
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
2022-07-18 00:09:03 +08:00
|
|
|
/* AMT gateway side message handler queue */
|
|
|
|
struct amt_events events[AMT_MAX_EVENTS];
|
|
|
|
u8 event_idx;
|
|
|
|
u8 nr_events;
|
2021-11-01 00:00:02 +08:00
|
|
|
};
|
|
|
|
|
2021-11-01 00:00:04 +08:00
|
|
|
#define AMT_TOS 0xc0
|
amt: add data plane of amt interface
Before forwarding multicast traffic, the amt interface establishes between
gateway and relay. In order to establish, amt defined some message type
and those message flow looks like the below.
Gateway Relay
------- -----
: Request :
[1] | N |
|---------------------->|
| Membership Query | [2]
| N,MAC,gADDR,gPORT |
|<======================|
[3] | Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR,gPORT |<-----------------() |
| *IP Packet(S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
~ ~
~ Request ~
[4] | N' |
|---------------------->|
| Membership Query | [5]
| N',MAC',gADDR',gPORT' |
|<======================|
[6] | |
| Teardown |
| N,MAC,gADDR,gPORT |
|---------------------->|
| | [7]
| Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR',gPORT' |<-----------------() |
| *IP Packet (S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
| |
: :
1. Discovery
- Sent by Gateway to Relay
- To find Relay unique ip address
2. Advertisement
- Sent by Relay to Gateway
- Contains the unique IP address
3. Request
- Sent by Gateway to Relay
- Solicit to receive 'Query' message.
4. Query
- Sent by Relay to Gateway
- Contains General Query message.
5. Update
- Sent by Gateway to Relay
- Contains report message.
6. Multicast Data
- Sent by Relay to Gateway
- encapsulated multicast traffic.
7. Teardown
- Not supported at this time.
Except for the Teardown message, it supports all messages.
In the next patch, IGMP/MLD logic will be added.
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-11-01 00:00:03 +08:00
|
|
|
#define AMT_IPHDR_OPTS 4
|
2021-11-01 00:00:05 +08:00
|
|
|
#define AMT_IP6HDR_OPTS 8
|
2021-11-01 00:00:04 +08:00
|
|
|
#define AMT_GC_INTERVAL (30 * 1000)
|
2021-11-01 00:00:02 +08:00
|
|
|
#define AMT_MAX_GROUP 32
|
|
|
|
#define AMT_MAX_SOURCE 128
|
|
|
|
#define AMT_HSIZE_SHIFT 8
|
|
|
|
#define AMT_HSIZE (1 << AMT_HSIZE_SHIFT)
|
|
|
|
|
amt: add data plane of amt interface
Before forwarding multicast traffic, the amt interface establishes between
gateway and relay. In order to establish, amt defined some message type
and those message flow looks like the below.
Gateway Relay
------- -----
: Request :
[1] | N |
|---------------------->|
| Membership Query | [2]
| N,MAC,gADDR,gPORT |
|<======================|
[3] | Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR,gPORT |<-----------------() |
| *IP Packet(S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
~ ~
~ Request ~
[4] | N' |
|---------------------->|
| Membership Query | [5]
| N',MAC',gADDR',gPORT' |
|<======================|
[6] | |
| Teardown |
| N,MAC,gADDR,gPORT |
|---------------------->|
| | [7]
| Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR',gPORT' |<-----------------() |
| *IP Packet (S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
| |
: :
1. Discovery
- Sent by Gateway to Relay
- To find Relay unique ip address
2. Advertisement
- Sent by Relay to Gateway
- Contains the unique IP address
3. Request
- Sent by Gateway to Relay
- Solicit to receive 'Query' message.
4. Query
- Sent by Relay to Gateway
- Contains General Query message.
5. Update
- Sent by Gateway to Relay
- Contains report message.
6. Multicast Data
- Sent by Relay to Gateway
- encapsulated multicast traffic.
7. Teardown
- Not supported at this time.
Except for the Teardown message, it supports all messages.
In the next patch, IGMP/MLD logic will be added.
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-11-01 00:00:03 +08:00
|
|
|
#define AMT_DISCOVERY_TIMEOUT 5000
|
|
|
|
#define AMT_INIT_REQ_TIMEOUT 1
|
2021-11-01 00:00:02 +08:00
|
|
|
#define AMT_INIT_QUERY_INTERVAL 125
|
amt: add data plane of amt interface
Before forwarding multicast traffic, the amt interface establishes between
gateway and relay. In order to establish, amt defined some message type
and those message flow looks like the below.
Gateway Relay
------- -----
: Request :
[1] | N |
|---------------------->|
| Membership Query | [2]
| N,MAC,gADDR,gPORT |
|<======================|
[3] | Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR,gPORT |<-----------------() |
| *IP Packet(S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
~ ~
~ Request ~
[4] | N' |
|---------------------->|
| Membership Query | [5]
| N',MAC',gADDR',gPORT' |
|<======================|
[6] | |
| Teardown |
| N,MAC,gADDR,gPORT |
|---------------------->|
| | [7]
| Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR',gPORT' |<-----------------() |
| *IP Packet (S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
| |
: :
1. Discovery
- Sent by Gateway to Relay
- To find Relay unique ip address
2. Advertisement
- Sent by Relay to Gateway
- Contains the unique IP address
3. Request
- Sent by Gateway to Relay
- Solicit to receive 'Query' message.
4. Query
- Sent by Relay to Gateway
- Contains General Query message.
5. Update
- Sent by Gateway to Relay
- Contains report message.
6. Multicast Data
- Sent by Relay to Gateway
- encapsulated multicast traffic.
7. Teardown
- Not supported at this time.
Except for the Teardown message, it supports all messages.
In the next patch, IGMP/MLD logic will be added.
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-11-01 00:00:03 +08:00
|
|
|
#define AMT_MAX_REQ_TIMEOUT 120
|
|
|
|
#define AMT_MAX_REQ_COUNT 3
|
|
|
|
#define AMT_SECRET_TIMEOUT 60000
|
2021-11-01 00:00:02 +08:00
|
|
|
#define IANA_AMT_UDP_PORT 2268
|
|
|
|
#define AMT_MAX_TUNNELS 128
|
|
|
|
#define AMT_MAX_REQS 128
|
|
|
|
#define AMT_GW_HLEN (sizeof(struct iphdr) + \
|
|
|
|
sizeof(struct udphdr) + \
|
|
|
|
sizeof(struct amt_gw_headers))
|
|
|
|
#define AMT_RELAY_HLEN (sizeof(struct iphdr) + \
|
|
|
|
sizeof(struct udphdr) + \
|
|
|
|
sizeof(struct amt_relay_headers))
|
|
|
|
|
|
|
|
static inline bool netif_is_amt(const struct net_device *dev)
|
|
|
|
{
|
|
|
|
return dev->rtnl_link_ops && !strcmp(dev->rtnl_link_ops->kind, "amt");
|
|
|
|
}
|
|
|
|
|
amt: add data plane of amt interface
Before forwarding multicast traffic, the amt interface establishes between
gateway and relay. In order to establish, amt defined some message type
and those message flow looks like the below.
Gateway Relay
------- -----
: Request :
[1] | N |
|---------------------->|
| Membership Query | [2]
| N,MAC,gADDR,gPORT |
|<======================|
[3] | Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR,gPORT |<-----------------() |
| *IP Packet(S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
~ ~
~ Request ~
[4] | N' |
|---------------------->|
| Membership Query | [5]
| N',MAC',gADDR',gPORT' |
|<======================|
[6] | |
| Teardown |
| N,MAC,gADDR,gPORT |
|---------------------->|
| | [7]
| Membership Update |
| ({G:INCLUDE({S})}) |
|======================>|
| |
---------------------:-----------------------:---------------------
| | | |
| | *Multicast Data | *IP Packet(S,G) |
| | gADDR',gPORT' |<-----------------() |
| *IP Packet (S,G) |<======================| |
| ()<-----------------| | |
| | | |
---------------------:-----------------------:---------------------
| |
: :
1. Discovery
- Sent by Gateway to Relay
- To find Relay unique ip address
2. Advertisement
- Sent by Relay to Gateway
- Contains the unique IP address
3. Request
- Sent by Gateway to Relay
- Solicit to receive 'Query' message.
4. Query
- Sent by Relay to Gateway
- Contains General Query message.
5. Update
- Sent by Gateway to Relay
- Contains report message.
6. Multicast Data
- Sent by Relay to Gateway
- encapsulated multicast traffic.
7. Teardown
- Not supported at this time.
Except for the Teardown message, it supports all messages.
In the next patch, IGMP/MLD logic will be added.
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-11-01 00:00:03 +08:00
|
|
|
static inline u64 amt_gmi(const struct amt_dev *amt)
|
|
|
|
{
|
|
|
|
return ((amt->qrv * amt->qi) + amt->qri) * 1000;
|
|
|
|
}
|
|
|
|
|
2021-11-01 00:00:02 +08:00
|
|
|
#endif /* _NET_AMT_H_ */
|