netdev - Re: Printing the driver name as part of the netdev watchdog message

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

Message-Id: <20080706.155318.46569612.davem@davemloft.net>
Date:	Sun, 06 Jul 2008 15:53:18 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	arjan@...radead.org
Cc:	netdev@...r.kernel.org
Subject: Re: Printing the driver name as part of the netdev watchdog message

From: Arjan van de Ven <arjan@...radead.org>
Date: Sun, 6 Jul 2008 13:08:01 -0700

> Does this patch look like the right approach for achieving the goal?

It's almost there.

You can issue an ethtool_ops->get_drvinfo() call, on devices which
support ethtool, and fetch the driver info from there.

Your current method of obtaining this info can be used as the
fallback when the ethtool op fails.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html