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
| ||
|
Message-ID: <CAM_iQpXTw3MsrT=C3rotH6hppVY6gi9KE7JARRayf7WZPz97zg@mail.gmail.com> Date: Wed, 20 Feb 2019 14:36:45 -0800 From: Cong Wang <xiyou.wangcong@...il.com> To: Vlad Buslov <vladbu@...lanox.com> Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>, Jamal Hadi Salim <jhs@...atatu.com>, Jiri Pirko <jiri@...nulli.us>, David Miller <davem@...emloft.net> Subject: Re: [PATCH net-next 12/12] net: sched: flower: set unlocked flag for flower proto ops On Tue, Feb 19, 2019 at 2:15 AM Vlad Buslov <vladbu@...lanox.com> wrote: > > > On Mon 18 Feb 2019 at 19:27, Cong Wang <xiyou.wangcong@...il.com> wrote: > > On Wed, Feb 13, 2019 at 11:47 PM Vlad Buslov <vladbu@...lanox.com> wrote: > >> > >> Set TCF_PROTO_OPS_DOIT_UNLOCKED for flower classifier to indicate that its > >> ops callbacks don't require caller to hold rtnl lock. > > > > So, if this means RTNL is gone for all cls_flower changes, why > > do I still see rtnl_lock() in cls_flower.c after all your patches in > > this set? > > It doesn't say that rtnl lock is gone, what it says is that caller > doesn't have to obtain rtnl lock before calling flower ops callbacks. So RTNL lock is still a bottle neck after all of these patches, isn't it? :) Yeah, please kindly add an explanation for why RTNL lock is still here. Thanks.
Powered by blists - more mailing lists