netdev - Re: [PATCH net-next v3 11/12] net: sched: flower: track rtnl lock state

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: <20190321141109.GO2087@nanopsycho>
Date:   Thu, 21 Mar 2019 15:11:09 +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, sbrivio@...hat.com
Subject: Re: [PATCH net-next v3 11/12] net: sched: flower: track rtnl lock
 state

Thu, Mar 21, 2019 at 02:17:43PM CET, vladbu@...lanox.com wrote:
>Use 'rtnl_held' flag to track if caller holds rtnl lock. Propagate the flag
>to internal functions that need to know rtnl lock state. Take rtnl lock
>before calling tcf APIs that require it (hw offload, bind filter, etc.).
>
>Signed-off-by: Vlad Buslov <vladbu@...lanox.com>
>Reviewed-by: Stefano Brivio <sbrivio@...hat.com>

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