| 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
| ||
|
Date: Sat, 14 Jun 2008 00:14:28 -0700 (PDT) From: David Miller <davem@...emloft.net> To: mingo@...e.hu Cc: torvalds@...ux-foundation.org, akpm@...ux-foundation.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, rjw@...k.pl Subject: Re: [GIT]: Networking From: Ingo Molnar <mingo@...e.hu> Date: Sat, 14 Jun 2008 08:27:58 +0200 > just to clarify the bug pattern: the box was still accessible after the > warning. So this is a far less serious problem and i'd suggest we open > up a separate regression entry for it and consider the hung-TCP problem > closed. (i havent seen the hang in the last week, with either version of > the tcp-accept reverts) It is a warning that just means the transmitted on the network device stalled for an unusually long period of time. Is your subnet flooded when these warnings occur? Is the remove side system wedged or at a very high load when the message triggers? All of these would be useful points of information to determine if this might be normal or not. In theory, if the remove port the device is connected to gets extremely congested, emits a pause frame to your machine, but never releases that pause, this (new) warning could trigger. This warning was added by Arjan in 2.6.25 FYI in order to diagnose the not-normal cases better. -- 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