* [PATCH v3 net-next] sock: Reset dst when changing sk_mark via setsockopt
@ 2018-11-08 14:13 David Barmann
2018-11-08 15:16 ` Eric Dumazet
2018-11-09 3:36 ` David Miller
0 siblings, 2 replies; 3+ messages in thread
From: David Barmann @ 2018-11-08 14:13 UTC (permalink / raw)
To: netdev
When setting the SO_MARK socket option, if the mark changes, the dst
needs to be reset so that a new route lookup is performed.
This fixes the case where an application wants to change routing by
setting a new sk_mark. If this is done after some packets have already
been sent, the dst is cached and has no effect.
Signed-off-by: David Barmann <david.barmann@stackpath.com>
---
net/core/sock.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/net/core/sock.c b/net/core/sock.c
index 7b304e454a38..6d7e189e3cd9 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -952,10 +952,12 @@ int sock_setsockopt(struct socket *sock, int level, int optname,
clear_bit(SOCK_PASSSEC, &sock->flags);
break;
case SO_MARK:
- if (!ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN))
+ if (!ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN)) {
ret = -EPERM;
- else
+ } else if (val != sk->sk_mark) {
sk->sk_mark = val;
+ sk_dst_reset(sk);
+ }
break;
case SO_RXQ_OVFL:
--
2.14.5
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v3 net-next] sock: Reset dst when changing sk_mark via setsockopt
2018-11-08 14:13 [PATCH v3 net-next] sock: Reset dst when changing sk_mark via setsockopt David Barmann
@ 2018-11-08 15:16 ` Eric Dumazet
2018-11-09 3:36 ` David Miller
1 sibling, 0 replies; 3+ messages in thread
From: Eric Dumazet @ 2018-11-08 15:16 UTC (permalink / raw)
To: David Barmann, netdev
On 11/08/2018 06:13 AM, David Barmann wrote:
> When setting the SO_MARK socket option, if the mark changes, the dst
> needs to be reset so that a new route lookup is performed.
>
> This fixes the case where an application wants to change routing by
> setting a new sk_mark. If this is done after some packets have already
> been sent, the dst is cached and has no effect.
>
> Signed-off-by: David Barmann <david.barmann@stackpath.com>
> ---
Reviewed-by: Eric Dumazet <edumazet@google.com>
Thanks David !
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v3 net-next] sock: Reset dst when changing sk_mark via setsockopt
2018-11-08 14:13 [PATCH v3 net-next] sock: Reset dst when changing sk_mark via setsockopt David Barmann
2018-11-08 15:16 ` Eric Dumazet
@ 2018-11-09 3:36 ` David Miller
1 sibling, 0 replies; 3+ messages in thread
From: David Miller @ 2018-11-09 3:36 UTC (permalink / raw)
To: david.barmann; +Cc: netdev
From: David Barmann <david.barmann@stackpath.com>
Date: Thu, 8 Nov 2018 08:13:35 -0600
> When setting the SO_MARK socket option, if the mark changes, the dst
> needs to be reset so that a new route lookup is performed.
>
> This fixes the case where an application wants to change routing by
> setting a new sk_mark. If this is done after some packets have already
> been sent, the dst is cached and has no effect.
>
> Signed-off-by: David Barmann <david.barmann@stackpath.com>
Applied.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-11-09 13:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-08 14:13 [PATCH v3 net-next] sock: Reset dst when changing sk_mark via setsockopt David Barmann
2018-11-08 15:16 ` Eric Dumazet
2018-11-09 3:36 ` David Miller
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.