linux-kernel - Re: Problem with modprobe

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] [day] [month] [year] [list]

Message-ID: <93c93732-70e8-ad8a-bb2e-a5da315742e1@lwfinger.net>
Date:   Tue, 27 Sep 2022 13:25:15 -0500
From:   Larry Finger <Larry.Finger@...inger.net>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: Problem with modprobe

Greg,

On 9/27/22 12:35, Greg KH wrote:
> I don't think we ever auto-unload dependant modules as we don't know if
> they are still in use or not (hint, module references is not a
> representation if the module is in use or not.)
> 
> So this is working as intended, right?  And how it's always worked?

Thanks for the explanation.I will need to document this behavior and explain to 
the users that it takes two steps to unload. At least the load works correctly.

Thanks again,

Larry