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-next>] [day] [month] [year] [list]
Message-ID: <6c1ca180-8df7-c4d0-bd9f-d6b70f6c5142@lwfinger.net>
Date:   Tue, 27 Sep 2022 12:11:24 -0500
From:   Larry Finger <Larry.Finger@...inger.net>
To:     LKML <linux-kernel@...r.kernel.org>,
        linux-wireless <linux-wireless@...r.kernel.org>
Cc:     Greg KH <gregkh@...uxfoundation.org>
Subject: Problem with modprobe

Hi,

The driver for the Realtek RTL8821CE network card show some asymmetrical 
behavior between loading and unloading.

Starting from scratch, a load command provides the expected results:

finger@...alhost:~/rtw88>sudo modprobe -v rtw88_8821ce
insmod 
/lib/modules/6.1.0-rc3-wireless-next-00623-g2bc09edc7fa2-dirty/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko 

insmod 
/lib/modules/6.1.0-rc3-wireless-next-00623-g2bc09edc7fa2-dirty/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko 

insmod 
/lib/modules/6.1.0-rc3-wireless-next-00623-g2bc09edc7fa2-dirty/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko 

insmod 
/lib/modules/6.1.0-rc3-wireless-next-00623-g2bc09edc7fa2-dirty/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko

Unloading produces a different result:

finger@...alhost:~/rtw88>sudo modprobe -rv rtw88_8821ce
rmmod rtw88_8821ce
rmmod rtw88_pci
rmmod rtw88_8821c

Note that rtw88_core is still loaded and needs to be unloaded separately:

finger@...alhost:~/rtw88>sudo modprobe -rv rtw88_core
rmmod rtw88_core

The appropriate lines from modules.dep reformatted for clarity are as follows:

kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko:
    kernel/net/mac80211/mac80211.ko
    kernel/lib/crypto/libarc4.ko
    kernel/net/wireless/cfg80211.ko
kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko:
    kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko
    kernel/net/mac80211/mac80211.ko
    kernel/lib/crypto/libarc4.ko
    kernel/net/wireless/cfg80211.ko
kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko:
    kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko
    kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko
    kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko
    kernel/net/mac80211/mac80211.ko
    kernel/lib/crypto/libarc4.ko
    kernel/net/wireless/cfg80211.ko
kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko:
    kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko
    kernel/net/mac80211/mac80211.ko
    kernel/lib/crypto/libarc4.ko
    kernel/net/wireless/cfg80211.ko

What is the explanation for the failure to auto-unload rtw88_core?

Thanks,

Larry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ