From: Martin Josefsson (gandalf_at_wlug.westbo.se)
Date: Tue 01 Apr 2003 - 11:33:24 BST
On Tue, 2003-04-01 at 02:36, Lyashkov Alex wrote:
> > in init() you read_unlock(&s_context_lock); when it should be read_lock
> what file have this bug? example please.
> grep -n -e read_lock -e read_unlock *
>
> iptable_mangle.c:222: read_lock(&s_context_lock);
> iptable_mangle.c:237: read_unlock(&s_context_lock);
>
> iptable_mangle.c:276: read_lock(&s_context_lock);
> iptable_mangle.c:285: read_unlock(&s_context_lock);
>
> iptable_mangle.c:298: read_lock(&s_context_lock);
> iptable_mangle.c:307: read_unlock(&s_context_lock);
Ok, not all but a few have a read_unlock() instead of a read_lock() when
trying to lock the s_context_lock.
arp_tables.c
ip_tables.c
ipt_LOG.c
ipt_MARK.c
ipt_MASQUERADE.c
ipt_MIRROR.c
ipt_REDIRECT.c
ipt_REJECT.c
ipt_TCPMSS.c
ipt_TOS.c
ipt_ah.c
-- /Martin