netdev - Re: one more... iproute commands lockup whole system

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:	Wed, 04 Apr 2007 03:39:12 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	hadi@...erus.ca
CC:	Denys <denys@...p.net.lb>,
	Stephen Hemminger <shemminger@...ux-foundation.org>,
	netdev@...r.kernel.org
Subject: Re: one more... iproute commands lockup whole system

jamal wrote:
> On Wed, 2007-04-04 at 03:03 +0300, Denys wrote:
> 
>>I'm not sure it is mistake or error, but i feel it is dangerous, cause 
>>commands locking up the system, no kernel panic, no oops, so only watchdog 
>>can save poor server (and not sure this even)
>>
>>Commands to lockup system (just i am giving my example, i didnt sort out what 
>>exactly locked up system, i guess redirecting to eth0.5, which is not 
>>intended for that):
> 
> 
> read:
> doc/actions/mirred-usage


Are you refering to "What NOT to do if you dont want your machine to
crash:"? I think we should make sure users can't even accidentally
crash their box, so this should at least be caught at runtime.
I thought the TTL stuff was intended to avoid this ..

-
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