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] [day] [month] [year] [list]
Date:   Fri, 7 Aug 2020 17:30:16 +0900
From:   Yoshiki Komachi <>
To:     David Ahern <>,
        John Fastabend <>
Cc:     "David S. Miller" <>,
        Alexei Starovoitov <>,
        Daniel Borkmann <>,
        Jesper Dangaard Brouer <>,
        Jakub Kicinski <>,
        Martin KaFai Lau <>,
        Song Liu <>, Yonghong Song <>,
        Andrii Nakryiko <>,
        KP Singh <>,
        Roopa Prabhu <>,
        Nikolay Aleksandrov <>,
        David Ahern <>,
        Networking <>,, bpf <>
Subject: Re: [RFC PATCH bpf-next 0/3] Add a new bpf helper for FDB lookup

> 2020/08/06 1:36、David Ahern <>のメール:
> On 8/5/20 4:26 AM, Yoshiki Komachi wrote:
>>> Just to clarify for myself. I expect that with just the helpers here
>>> we should only expect static configurations to work, e.g. any learning
>>> and/or aging is not likely to work if we do redirects in the XDP path.
>> As you described above, learning and aging don’t work at this point. 
>> IMO, another helper for learning will be required to fill the requirements.
>> I guess that the helper will enable us to use the aging feature as well
>> because the aging is the functionality of bridge fdb.
> One option is to have a flag that bumps the ageing on successful lookup
> and do that in 1 call. You will already have access to the fdb entry.

It seems like a good idea to me! I guess that the flags in my suggested bpf
helper for the FDB lookup will be useful for such a case.

Thanks & Best regards,

Yoshiki Komachi

Powered by blists - more mailing lists