netdev - Re: [PATCH net-next v3 13/16] net: sched: extend proto ops to support unlocked classifiers

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: <20190205132935.GK2133@nanopsycho>
Date:   Tue, 5 Feb 2019 14:29:35 +0100
From:   Jiri Pirko <jiri@...nulli.us>
To:     Vlad Buslov <vladbu@...lanox.com>
Cc:     netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
        davem@...emloft.net, ast@...nel.org, daniel@...earbox.net
Subject: Re: [PATCH net-next v3 13/16] net: sched: extend proto ops to
 support unlocked classifiers

Mon, Feb 04, 2019 at 01:32:58PM CET, vladbu@...lanox.com wrote:
>Add 'rtnl_held' flag to tcf proto change, delete, destroy, dump, walk
>functions to track rtnl lock status. Extend users of these function in cls
>API to propagate rtnl lock status to them. This allows classifiers to
>obtain rtnl lock when necessary and to pass rtnl lock status to extensions
>and driver offload callbacks.
>
>Add flags field to tcf proto ops. Add flag value to indicate that
>classifier doesn't require rtnl lock.
>
>Signed-off-by: Vlad Buslov <vladbu@...lanox.com>

Acked-by: Jiri Pirko <jiri@...lanox.com>