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]

Date:	Sun, 06 Jul 2008 21:49:15 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	arjan@...radead.org
Cc:	wangchen@...fujitsu.com, 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 21:34:27 -0700

> On Sun, 06 Jul 2008 20:59:05 -0700 (PDT)
> David Miller <davem@...emloft.net> wrote:
> 
> > 
> > Also correct.
> 
> ok updated version below; I also added an explicit comment for the
> ethtool locking
> 
> From: Arjan van de Ven <arjan@...ux.intel.com>
> Subject: Use WARN_ONCE() in the netdev timeout handler (and print module name)

I'm basically fine with these changes.

But plain WARN() and WARN_ONCE() are not in any tree I am maintaining
at the moment, so I really can't add it to net-next-2.6 or net-2.6
even if I wanted to.

Do you really need this dependency?
--
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