linux-kernel - Query: consistent method for identifying watchdog driver

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>] [day] [month] [year] [list]

Message-ID: <20150810061017.GC4523@dhcppc13.redhat.com>
Date:	Mon, 10 Aug 2015 11:40:17 +0530
From:	Pratyush Anand <panand@...hat.com>
To:	linux-watchdog@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, dyoung@...hat.com
Subject: Query: consistent method for identifying watchdog driver

Hi Watchdog Folks,

I need some way to identify the driver/module for a given watchdog node say
/dev/watchdog0.

Documentation/watchdog/watchdog-api.txt says:
identity                a string identifying the watchdog driver

However, all the watchdog driver does not define identity as DRV_NAME.

Otherway, could be to look for /sys/class/watchdog/watchdog0/device/modalias.

However, for all wd devices(say drivers/misc/mei/wd.c) we do not see an entry
for /sys/class/watchdog/watchdog0/device/. Reason is that parent of
watchdog_device has not been assigned for such devices. I will send fixup for
all such watchdog devices anyway. But, I wanted to know that what could be the
best way to identify the driver.

Thanks for your help.

~Pratyush
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/