netdev - Re: [PATCH v3 net-next] sock: Reset dst when changing sk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <093ffd5f-d31c-4eb1-cb86-6c0d87a25e78@gmail.com>
Date:   Thu, 8 Nov 2018 07:16:43 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     David Barmann <david.barmann@...ckpath.com>,
        netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v3 net-next] sock: Reset dst when changing sk_mark via
 setsockopt



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@...ckpath.com>
> ---

Reviewed-by: Eric Dumazet <edumazet@...gle.com>

Thanks David !