netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: wangchen@cn.fujitsu.com, netdev@vger.kernel.org
Subject: Re: Printing the driver name as part of the netdev watchdog message
Date: Mon, 7 Jul 2008 08:23:51 -0700	[thread overview]
Message-ID: <20080707082351.0cf77eda@infradead.org> (raw)
In-Reply-To: <20080706.234433.172895242.davem@davemloft.net>

On Sun, 06 Jul 2008 23:44:33 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:

> From: Arjan van de Ven <arjan@infradead.org>
> Date: Sun, 6 Jul 2008 21:57:11 -0700
> 
> > one option is that I carry this patch in the WARN tree (which I
> > plan to submit for -next tomorrow)
> 
> It's going to be a conflict field day with net-next-2.6 especially
> with some changes I have coming in there soon, otherwise I'd say
> that yes that would be the way to do.

ok

if you merge the piece below (which is just the core), I can do the WARN()
part later when the dust has settled (it's a one liner anyway pretty much)

--

From: Arjan van de Ven <arjan@linux.intel.com>
Subject: Print the driver name as part of the WATCHDOG message

As suggested by Dave:

This patch adds a function to get the driver name from a struct net_device,
and consequently uses this in the watchdog timeout handler to print as 
part of the message. 

Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
---
 include/linux/netdevice.h |    3 +++
 net/core/dev.c            |   37 +++++++++++++++++++++++++++++++++++++
 net/sched/sch_generic.c   |    7 ++++---
 3 files changed, 44 insertions(+), 3 deletions(-)

Index: linux.trees.git/include/linux/netdevice.h
===================================================================
--- linux.trees.git.orig/include/linux/netdevice.h
+++ linux.trees.git/include/linux/netdevice.h
@@ -1514,6 +1514,9 @@ extern void dev_seq_stop(struct seq_file
 extern int netdev_class_create_file(struct class_attribute *class_attr);
 extern void netdev_class_remove_file(struct class_attribute *class_attr);
 
+extern void netdev_drivername(struct net_device *dev, char *buffer, int len);
+
+
 extern void linkwatch_run_queue(void);
 
 extern int netdev_compute_features(unsigned long all, unsigned long one);
Index: linux.trees.git/net/core/dev.c
===================================================================
--- linux.trees.git.orig/net/core/dev.c
+++ linux.trees.git/net/core/dev.c
@@ -4554,6 +4554,43 @@ err_name:
 	return -ENOMEM;
 }
 
+void netdev_drivername(struct net_device *dev, char *buffer, int len)
+{
+	struct device_driver *driver;
+	struct device *parent;
+	struct ethtool_drvinfo info;
+	const struct ethtool_ops *ops = dev->ethtool_ops;
+
+	if (len <= 0)
+		return;
+	buffer[0] = 0;
+
+	/*
+	 * Note: in principle ethtool ops need to be called
+	 * with the RTNL mutex held, while this function is called
+	 * from IRQ context. However, get_drvinfo is a special exception
+	 * (confirmed by Dave and Jeff) and doesn't need the mutex.
+	 */
+	if (ops && ops->get_drvinfo) {
+		memset(&info, 0, sizeof(info));
+		info.cmd = ETHTOOL_GDRVINFO;
+		ops->get_drvinfo(dev, &info);
+		if (strlen(info.driver) > 0) {
+			strlcpy(buffer, info.driver, len);
+			return;
+		}
+	}
+
+	parent = dev->dev.parent;
+
+	if (!parent)
+		return;
+
+	driver = parent->driver;
+	if (driver && driver->name)
+		strlcpy(buffer, driver->name, len);
+}
+
 static void __net_exit netdev_exit(struct net *net)
 {
 	kfree(net->dev_name_head);
Index: linux.trees.git/net/sched/sch_generic.c
===================================================================
--- linux.trees.git.orig/net/sched/sch_generic.c
+++ linux.trees.git/net/sched/sch_generic.c
@@ -215,9 +215,10 @@ static void dev_watchdog(unsigned long a
 		    netif_carrier_ok(dev)) {
 			if (netif_queue_stopped(dev) &&
 			    time_after(jiffies, dev->trans_start + dev->watchdog_timeo)) {
-
-				printk(KERN_INFO "NETDEV WATCHDOG: %s: transmit timed out\n",
-				       dev->name);
+				char drivername[64];
+				netdev_drivername(dev, drivername, 64);
+				printk(KERN_INFO "NETDEV WATCHDOG: %s (%s): transmit timed out\n",
+				       dev->name, drivername);
 				dev->tx_timeout(dev);
 				WARN_ON_ONCE(1);
 			}

  reply	other threads:[~2008-07-07 15:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06 20:08 Printing the driver name as part of the netdev watchdog message Arjan van de Ven
2008-07-06 22:53 ` David Miller
2008-07-06 23:56   ` Arjan van de Ven
2008-07-07  1:51     ` Wang Chen
2008-07-07  3:59       ` David Miller
2008-07-07  4:34         ` Arjan van de Ven
2008-07-07  4:49           ` David Miller
2008-07-07  4:57             ` Arjan van de Ven
2008-07-07  6:44               ` David Miller
2008-07-07 15:23                 ` Arjan van de Ven [this message]
2008-07-07  1:08   ` Stephen Hemminger
2008-07-07  1:22     ` David Miller
2008-07-07  1:53       ` Jeff Garzik
2008-07-07 17:05         ` Stephen Hemminger
2008-07-07 22:45       ` Roland Dreier
2008-07-07 22:57         ` David Miller
2008-07-07 23:14           ` Roland Dreier
2008-07-07 23:44             ` Stephen Hemminger
2008-07-08  0:10               ` Arjan van de Ven
2008-07-08 19:13             ` Steve Wise
2008-07-08 21:31               ` David Miller
2008-07-08 21:47                 ` Arjan van de Ven
2008-07-08 21:57                   ` David Miller
2008-07-08 23:48                     ` Arjan van de Ven
2008-07-08 23:53                       ` David Miller
2008-07-09  0:17                         ` Arjan van de Ven
2008-07-09  1:44                         ` Arjan van de Ven
2008-07-09  3:16                           ` Stephen Hemminger
2008-07-09 17:20                             ` Joe Perches
2008-07-09 17:56                               ` Arjan van de Ven
2008-07-09 18:20                                 ` Joe Perches
2008-07-09 18:50                                   ` Arjan van de Ven
2008-07-09 18:28                                 ` Ben Hutchings

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080707082351.0cf77eda@infradead.org \
    --to=arjan@infradead.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=wangchen@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).