[PATCH v3 net-next] sock: Reset dst when changing sk_mark via setsockopt

and has no effect. Signed-off-by: David Barmann --- 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

[PATCH v2 net-next] sock: Reset dst when changing sk_mark via setsockopt

. Signed-off-by: David Barmann --- 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..c74b10be86cb 100644 --- a/net/core/sock.c +++ b/net/core/sock.c @@ -952,10 +952,12 @@ int sock_setsockopt(struct socket

Re: [PATCH net-next] sock: Reset dst when changing sk_mark via setsockopt

> On 11/07/2018 02:33 PM, David Barmann wrote: > > When setting the SO_MARK socket option, 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_

[PATCH net-next] sock: Reset dst when changing sk_mark via setsockopt

. Signed-off-by: David Barmann --- net/core/sock.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/net/core/sock.c b/net/core/sock.c index 6fcc4bc07d19..187badac24a3 100644 --- a/net/core/sock.c +++ b/net/core/sock.c @@ -950,10 +950,14 @@ int sock_setsockopt(struct socket