Commit 98a0824a authored Nov 30, 2006 by Al Viro Committed by David S. Miller Dec 02, 2006

[EBTABLES]: Deal with the worst-case behaviour in loop checks.



No need to revisit a chain we'd already finished with during
the check for current hook.  It's either instant loop (which
we'd just detected) or a duplicate work.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>

parent 40642f95

net/bridge/netfilter/ebtables.c

+3 −1

Original line number	Diff line number	Diff line
		@@ -717,7 +717,9 @@ static int check_chainloops(struct ebt_entries chain, struct ebt_cl_stack cl_s
		BUGPRINT("loop\n");
		return -1;
		}
		/* this can't be 0, so the above test is correct */
		if (cl_s[i].hookmask & (1 << hooknr))
		goto letscontinue;
		/* this can't be 0, so the loop test is correct */
		cl_s[i].cs.n = pos + 1;
		pos = 0;
		cl_s[i].cs.e = ((void *)e + e->next_offset);