Bug 193851

Summary:	fjes kernel module loads on many machines
Product:	Drivers	Reporter:	jsauer65
Component:	Network	Assignee:	drivers_network (drivers_network)
Status:	NEW ---
Severity:	normal	CC:	linux-ide, nick83ola
Priority:	P1
Hardware:	x86-64
OS:	Linux
Kernel Version:	4.10.0-rc6	Subsystem:
Regression:	No	Bisected commit-id:

Description jsauer65 2017-02-02 18:39:05 UTC

During my custom kernel configuration using "make localmodconfig" I noticed
that
the "fjes" driver was configured.
I wondered why this network driver was needed for my laptop, so I have done
some
research.
According this [1] linux-netdev mailing list entry, which introduces the fjes
module, it is only needed for Extended Partitions of Fujitsu Primequest 2000
series servers.
This mail [2] refers to a Fujitsu document in which these special Extended
Partitions are explained.
I am sure that I don't need this driver for my ThinkPad T450s.
Nevertheless it is loaded because of an ACPI device "PNP0C02" which is linked
to
the module [3].

See also:
https://lkml.org/lkml/2016/6/8/98
http://unix.stackexchange.com/questions/335238/is-it-normal-that-a-modalias-
matches-various-devices

Some other Debian user have the same issue:
https://lists.debian.org/debian-user/2017/01/msg00825.html

[1]https://marc.info/?l=linux-netdev&m=142951966404542&w=2
[2]https://lwn.net/Articles/655298/
[3] https://cateee.net/lkddb/web-lkddb/FUJITSU_ES.html

Comment 1 linux-ide 2017-11-26 18:28:55 UTC

The over generic alias: acpi*:PNP0C02:* is still the only alias there in fjes.ko.gz for kernel version 4.13.12 and will result in a match for most machines with hardware /sys/devices
because ACPI\PNP0C02 = General ID for reserving resources required by PnP motherboard registers. (Not device specific.)

Comment 2 Nicola Lunghi 2017-12-05 18:09:11 UTC

Still there on 4.14 kernel

the fjes module should be  removed/blackilisted?

see

https://lkml.org/lkml/2016/6/9/127

Any input from mantainer?