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 Jul 2022 21:23:21 -0400
From:   Alexander Aring <>
To:     Miquel Raynal <>
Cc:     Alexander Aring <>,
        Stefan Schmidt <>,
        linux-wpan - ML <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        Paolo Abeni <>,
        Eric Dumazet <>,
        Network Development <>,
        David Girault <>,
        Romuald Despres <>,
        Frederic Blain <>,
        Nicolas Schodet <>,
        Thomas Petazzoni <>
Subject: Re: [PATCH wpan-next 19/20] ieee802154: hwsim: Do not check the rtnl


On Fri, Jul 1, 2022 at 10:37 AM Miquel Raynal <> wrote:
> There is no need to ensure the rtnl is locked when changing a driver's
> channel. This cause issues when scanning and this is the only driver
> relying on it. Just drop this dependency because it does not seem
> legitimate.

switching channels relies on changing pib attributes, pib attributes
are protected by rtnl. If you experience issues here then it's
probably because you do something wrong. All drivers assuming here
that rtnl lock is held.

- Alex

Powered by blists - more mailing lists