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  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:	Fri, 31 Aug 2007 13:33:04 +0400
From:	Badalian Vyacheslav <>
To:	Jarek Poplawski <>
Subject: Re: Tc bug (kernel crash) more info

>> i not have testing mashine.
>> we have 2 mashine and dynamic routing. if 1 mashine down - all traffic 
>> go to second mashine.
>> I can test is on this mashines but i need that testing mashine will 
>> reboot on kernel panic (sysctl message). No freezes =)
>> Ok. i try 2.6.23-rc4.
> ...but without testing machine it can be too much risk! New versions
> of kernel can break your applications (sometimes they should be at
> least rebuilded).
> So, maybe you would better try this, 'less testing', version of my patch:
I risk only if RC kernel broke hardware. Mashines use only iptables and 
TC. All Scrips backuped.
But if i need to reboot PC by hand (if it freeze) i need drive to 
servers-room =)

 > BTW, I think after this BUG could be something more about other CPUs.
 > Could you check this?

I send to you all info that catch NETCONSOLE. i don't cut any info...

Now 1 mashine work at *"2.6.23-rc4-git2 
Backup mashine use 2.6.18*

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists