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  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]
Date:   Thu, 15 Dec 2022 13:16:59 -0800
From:   Jakub Kicinski <>
To:     David Decotigny <>
Cc:     David Ahern <>,
        "Mahesh Bandewar (महेश बंडेवार) " 
        <>, David Decotigny <>,
        "David S. Miller" <>,
        Eric Dumazet <>,
        Paolo Abeni <>,,,
        Nikolay Aleksandrov <>,
        "Denis V. Lunev" <>,
        Daniel Borkmann <>,
        Chen Zhongjin <>,
        Yuwei Wang <>,
        Alexander Mikhalitsyn <>,
        Thomas Zeitlhofer <>
Subject: Re: [PATCH v1 1/1] net: neigh: persist proxy config across link

On Thu, 15 Dec 2022 12:36:32 -0800 David Decotigny wrote:
> > Makes sense. This is not urgent, tho, right?  
> Not that kind of urgent.
> FTR, in the v2 you suggested to use NUD_PERMANENT,

I think that was Alex. I don't have a strong preference. I could see
arguments being made in both directions (basically whether it's more
important to leave objects which are clearly not cache vs we care 
more about consistent behavior based on the permanent flag itself).

Let's limit the reposts until experts are in town ;)

>  I can try to see how this would look like. Note that this will make
> the patch larger and more intrusive, and with potentially a behavior
> change for whoever uses the netlink API directly instead of the
> iproute2 implementation for ip neigh X proxy things.

Powered by blists - more mailing lists