Yes, this error was corrected by Andi already :)
Thank you Ingo but this patch was already suggested by me previously (
http://marc.info/?l=linux-netdev&m=120361996713007&w=2 ) and was
rejected, since we can very easily consume all stack space, especially
with 4K stacks.
(try with NFS mounts and XFS for example)
Only safe way is to check available free stack space, since we can nest
loopback_xmit() several time.
In case of protocol errors (like in TCP, if we answer to an ACK by
another ACK, or ICMP loops), we would exhaust stack instead of delaying
packets for next softirq run.
Problem is to check available space :
It depends on stack growing UP or DOWN, and depends on caller running on
process stack, or softirq stack, or even hardirq stack.
--