Folks, One of my colleagues has caused DCCP to crash the kernel. This is when ttcp tries to use an unreachable route as I read it. This is a reproducible crash.
I will try and reproduce this when I have time with full logs and will add to ToDo as well when I have time but just to let people know in case somebody knows straight away where it is. I know I haven't supplied the full bug report etc and will do as time permits.. Ian ---------- Forwarded message ---------- From: Matt Jervis <[EMAIL PROTECTED]> Date: 12-Oct-2005 10:46 Subject: TTCP crash To: Ian McDonald <[EMAIL PROTECTED]> As per our conversation. The configuration was: +---------+ +---------+ +---------+ | 6 | 10.0.6.6 <===> 10.0.6.9 | 9 | 10.0.6.14 <===> 10.0.14.14 | 9 | +---------+ +---------+ +---------+ However the interfaces weren't configured on machine 9. +---------+ +---------+ +---------+ | 6 | 10.0.6.6 <===> x | 9 | x <===> 10.0.14.14 | 9 | +---------+ +---------+ +---------+ TTCP receiver was running on machine 14, and I attempted to run TTCP client on machine 6: ./ttcp_acme -l256 -v -c -n100 -t 10.0.14.14 ttcp-t: buflen=256, nbuf=100, align=16384/+0, port=5001 dccp(inet) -> 10.0.14.14 ttcp-t: socket Read from remote host machine6: Connection reset by peer Connection to machine6 closed. Initially the machine locked up, and it wasn't until the machine was rebooted that the last two lines came up. NB I didn't check at the serial port whether it had locked up, but it rebooted itself (via the setting in grub). Cheers, -- Matt Jervis WAND Group Computer Science Department, University of Waikato New Zealand email: <[EMAIL PROTECTED]> phone: +64 7 838 4466 ex 6651 - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
