* Re: [net-next,v1] net: e1000e: solve insmod 'Unknown symbol mutex_lock' error
[not found] <20210917141146.5822-1-chenhaoa@uniontech.com>
@ 2021-09-17 16:01 ` Jesse Brandeburg
0 siblings, 0 replies; only message in thread
From: Jesse Brandeburg @ 2021-09-17 16:01 UTC (permalink / raw)
To: Hao Chen
Cc: anthony.l.nguyen, davem, kuba, intel-wired-lan, netdev, linux-kernel
On 9/17/2021 7:11 AM, Hao Chen wrote:
> After I turn on the CONFIG_LOCK_STAT=y, insmod e1000e.ko will report:
> [ 5.641579] e1000e: Unknown symbol mutex_lock (err -2)
> [ 90.775705] e1000e: Unknown symbol mutex_lock (err -2)
> [ 132.252339] e1000e: Unknown symbol mutex_lock (err -2)
>
> This problem fixed after include <linux/mutex.h>.
Thanks for taking the time to send a patch.
Why do you think including a file will fix this? That error is usually
the user's fault for trying to use insmod which doesn't check module
dependencies.
The advice I usually give is to try modprobe instead, does the problem
still occur without this patch and just using modprobe?
^ permalink raw reply [flat|nested] only message in thread