netdev - Re: [PATCH net-next v3 11/16] net: sched: track rtnl lock status when validating extensions

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]

Date:   Tue, 5 Feb 2019 14:09:03 +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 11/16] net: sched: track rtnl lock status
 when validating extensions

Mon, Feb 04, 2019 at 01:32:56PM CET, vladbu@...lanox.com wrote:
>Actions API is already updated to not rely on rtnl lock for
>synchronization. However, it need to be provided with rtnl status when
>called from classifiers API in order to be able to correctly release the
>lock when loading kernel module.
>
>Extend extension validation function with 'rtnl_held' flag which is passed
>to actions API. Add new 'rtnl_held' parameter to tcf_exts_validate() in cls
>API. No classifier is currently updated to support unlocked execution, so
>pass hardcoded 'true' flag parameter value.
>
>Signed-off-by: Vlad Buslov <vladbu@...lanox.com>

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