Re: [BUG] DCCP : Suspected race in ackvec code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/28/06, Ian McDonald <imcdnzl@xxxxxxxxx> wrote:
> When send_ackvec sysctl is on DCCP locks the machine. Unfortunately it
> doesn't send any output to the kernel.

I'm getting below results by just stopping the syslog daemon and setting
printk log level to 9:

[root@qemu ~]# service syslog stop
[root@qemu ~]# echo 9 > /proc/sys/kernel/printk

With this the printk messages goes to the console, allowing us to see the
dccp_pr_debug messages till the very moment when a soft lockup happens
at dccp_ackvec_parse.

[root@qemu ~]# modprobe dccp dccp_debug=1
[root@qemu ~]# echo 3 > /proc/sys/net/dccp/default/rx_ccid
[root@qemu ~]# echo 3 > /proc/sys/net/dccp/default/tx_ccid

Oh well, not reproducing it right now, try with these settings to see you
reproduce it in your setup.

Regards,

- Arnaldo
-
: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux