netdev - Re: [PATCH] net/ncsi: Fix re-registering ncsi device

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACPK8Xd3MfTbp2184e6Hp7D4U40ku0vqw=pb5E7mamddMGnj3A@mail.gmail.com>
Date:   Thu, 12 Nov 2020 01:11:04 +0000
From:   Joel Stanley <joel@....id.au>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Samuel Mendoza-Jonas <sam@...dozajonas.com>,
        "David S . Miller" <davem@...emloft.net>,
        Andrew Jeffery <andrew@...id.au>,
        Networking <netdev@...r.kernel.org>
Subject: Re: [PATCH] net/ncsi: Fix re-registering ncsi device

On Thu, 12 Nov 2020 at 00:57, Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Thu, 12 Nov 2020 11:10:21 +1030 Joel Stanley wrote:
> > If a user unbinds and re-binds a ncsi aware driver, the kernel will
> > attempt to register the netlink interface at runtime. The structure is
> > marked __ro_after_init so this fails at this point.
>
> netlink family should be registered at module init and unregistered at
> unload. That's a better fix IMO.

I don't follow, isn't that what is implemented already?

Perhaps I'm getting confused because the systems that use this code
build the drivers in. The bug I'm seeing is when we unbind and re-bind
the driver without any module loading or unloading.