Re: timer_bh behaviour incorrect for 2.2.13?

kuznet@ms2.inr.ac.ru
Thu, 9 Dec 1999 19:42:32 +0300 (MSK)


Hello!

> you have missed the _real_ reason why the above 'bug' was there. It's a
> feature and prevents denial of service attacks. Especially wrt. networking
> it's very easy to flood a box with bh traffic, and if we are not careful
> then slower systems (routers) can effectively be locked up just by
> bombarding them with small/tricky packets. So we were always intentionally
> trying to guarantee that bhs do not get rerun infinitely.

You can borrow solution from softnet. It accumulates once ran softirqs
to mask and exit only when all pending BHs are ran once.

Alexey

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