mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-25 03:55:09 +08:00
7026b1ddb6
On the output paths in particular, we have to sometimes deal with two socket contexts. First, and usually skb->sk, is the local socket that generated the frame. And second, is potentially the socket used to control a tunneling socket, such as one the encapsulates using UDP. We do not want to disassociate skb->sk when encapsulating in order to fix this, because that would break socket memory accounting. The most extreme case where this can cause huge problems is an AF_PACKET socket transmitting over a vxlan device. We hit code paths doing checks that assume they are dealing with an ipv4 socket, but are actually operating upon the AF_PACKET one. Signed-off-by: David S. Miller <davem@davemloft.net>
30 lines
878 B
C
30 lines
878 B
C
#ifndef _NET_DN_NEIGH_H
|
|
#define _NET_DN_NEIGH_H
|
|
|
|
/*
|
|
* The position of the first two fields of
|
|
* this structure are critical - SJW
|
|
*/
|
|
struct dn_neigh {
|
|
struct neighbour n;
|
|
__le16 addr;
|
|
unsigned long flags;
|
|
#define DN_NDFLAG_R1 0x0001 /* Router L1 */
|
|
#define DN_NDFLAG_R2 0x0002 /* Router L2 */
|
|
#define DN_NDFLAG_P3 0x0004 /* Phase III Node */
|
|
unsigned long blksize;
|
|
__u8 priority;
|
|
};
|
|
|
|
void dn_neigh_init(void);
|
|
void dn_neigh_cleanup(void);
|
|
int dn_neigh_router_hello(struct sock *sk, struct sk_buff *skb);
|
|
int dn_neigh_endnode_hello(struct sock *sk, struct sk_buff *skb);
|
|
void dn_neigh_pointopoint_hello(struct sk_buff *skb);
|
|
int dn_neigh_elist(struct net_device *dev, unsigned char *ptr, int n);
|
|
int dn_to_neigh_output(struct sock *sk, struct sk_buff *skb);
|
|
|
|
extern struct neigh_table dn_neigh_table;
|
|
|
|
#endif /* _NET_DN_NEIGH_H */
|