[IPV4/IPV6]: Always wait for IPSEC SA resolution in socket contexts.
Do this even for non-blocking sockets. This avoids the silly -EAGAIN
that applications can see now, even for non-blocking sockets in some
cases (f.e. connect()).
With help from Venkat Tekkirala.
Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- include/net/route.h 3 additions, 2 deletionsinclude/net/route.h
- net/dccp/ipv4.c 1 addition, 1 deletionnet/dccp/ipv4.c
- net/dccp/ipv6.c 1 addition, 1 deletionnet/dccp/ipv6.c
- net/ipv4/af_inet.c 1 addition, 1 deletionnet/ipv4/af_inet.c
- net/ipv4/datagram.c 1 addition, 1 deletionnet/ipv4/datagram.c
- net/ipv4/raw.c 1 addition, 1 deletionnet/ipv4/raw.c
- net/ipv4/tcp_ipv4.c 1 addition, 1 deletionnet/ipv4/tcp_ipv4.c
- net/ipv4/udp.c 1 addition, 1 deletionnet/ipv4/udp.c
- net/ipv6/datagram.c 1 addition, 1 deletionnet/ipv6/datagram.c
- net/ipv6/raw.c 1 addition, 1 deletionnet/ipv6/raw.c
- net/ipv6/tcp_ipv6.c 1 addition, 1 deletionnet/ipv6/tcp_ipv6.c
- net/ipv6/udp.c 1 addition, 1 deletionnet/ipv6/udp.c
Loading
Please register or sign in to comment