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:   Tue, 19 May 2020 15:30:59 +0100
From:   Edward Cree <>
To:     Vlad Buslov <>
CC:     <>, <>,
        <>, <>, <>,
        <>, <>,
Subject: Re: [PATCH net-next v2 0/4] Implement classifier-action terse dump

On 19/05/2020 10:04, Vlad Buslov wrote:
> On Mon 18 May 2020 at 18:37, Edward Cree <> wrote:
>> I.e. if next year it turns out that some
>>  user needs one parameter that's been omitted here, but not the whole dump,
>>  are they going to want to add another mode to the uapi?
> Why not just extend terse dump? I won't break user land unless you are
> removing something from it.
But then all terse dump users pay the performance cost for thatone
 app's extra need.

> - Generic data is covered by current terse dump implementation.
>   Everything else will be act or cls specific
Fair point.
I don't suppose something something BPF mumble solve this? I haven't
 been following the BPF dumping work in detail but it sounds like it
 might be a cheap way to get the 'more performant next step' that
 was mentioned in the subthread with David.  Just a thought.


Powered by blists - more mailing lists