[systemd-devel] udev_device_get_driver implementation
gregkh at linuxfoundation.org
Wed Apr 24 16:38:41 UTC 2019
On Wed, Apr 24, 2019 at 08:38:02AM -0700, Sayeed hyder wrote:
> I was looking at the udev_device_get_driver implementation. It first gets
> the sys path and then appends "driver", and calls readlink to get the
> driver information. Does it work for all cases? While working on a project,
> I found that following the sys path, there is no "driver", but it should be
> "device/driver" i.e. if I append "device/driver" instead of "driver" only,
> I can use readlink to get the driver information.
What in-kernel driver causes an odd sysfs tree like this? Can you show
me the full path of it?
More information about the systemd-devel