Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Sender: Larry Finger <larry.finger@gmail.com>
Message-ID: <93c93732-70e8-ad8a-bb2e-a5da315742e1@lwfinger.net>
Date:   Tue, 27 Sep 2022 13:25:15 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.3.0
Subject: Re: Problem with modprobe
Content-Language: en-US
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     LKML <linux-kernel@vger.kernel.org>,
        linux-wireless <linux-wireless@vger.kernel.org>
References: <6c1ca180-8df7-c4d0-bd9f-d6b70f6c5142@lwfinger.net>
 <YzM0Z4gXsjZTDkX0@kroah.com>
From:   Larry Finger <Larry.Finger@lwfinger.net>
In-Reply-To: <YzM0Z4gXsjZTDkX0@kroah.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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