SysRq oddity with iptables logging

[Phil Oester]

On a heavily loaded gateway/firewall which performs quite a bit of logging (at
level DEBUG), I occasionally see iptables logs bleeding into SysRq data.
For example via serial:

telnet> send brk
m
SysRq : Show Memory
Mem-info:
DMA per-cpu:<7>EXT: IN=eth0 OUT=eth1 SRC=82.133.69.241 DST=10.2.242.181 LEN=98 TOS=0x00 PREC=0x00 TTL=20 ID=5087 PROTO=UDP SPT=60516 DPT=2967 LEN=78 

cpu 0 hot: low 2, high 6, batch 1
cpu 0 cold: low 0, high 2, batch 1
cpu 1 hot: low 2, high 6, batch 1
cpu 1 cold: low 0, high 2, batch 1

...

Note how the packet log just sandwiched itself in the middle of the data.

Is this expected behavior?

Phil Oester

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/