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: <20080729.134706.249036102.davem@davemloft.net>
Date:	Tue, 29 Jul 2008 13:47:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	arjan@...radead.org
Cc:	komurojun-mbn@...ty.com, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: NETDEV WATCHDOG: wifi0: transmit timed out

From: Arjan van de Ven <arjan@...radead.org>
Date: Tue, 29 Jul 2008 06:58:59 -0700

> On Tue, 29 Jul 2008 21:53:15 +0900
> Komuro <komurojun-mbn@...ty.com> wrote:
> 
> > Hi,
> > 
> > Please try to comment out the "WARN_ON_ONCE"
> > at net/sched/sched_generic.c.
> > 
> 
> "I have a hardware failure so I'll comment out the message that says
> so, and then I won't have a failure". Yeah that'll work well.

Yes, this is indeed a recidulious suggestion, to hide the problem
instead of trying to figure out what it might actually be.

Komuro has a serious problem accepting the fact that this condition is
in fact an abnormal error should should be logged, and he keeps
pushing to get this WARN_ON() removed over and over again.

I'm just ignoring him at this point.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ