From: Thomas Heinz <creatix@hipac.org>
To: netfilter-devel@lists.netfilter.org
Subject: ipt_do_table
Date: Wed, 07 Jan 2004 20:54:01 +0100 [thread overview]
Message-ID: <3FFC63D9.70705@hipac.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
Hi
Why does ipt_do_table use read_lock_bh instead of read_lock?
The concurrent counter snapshot resp. table modification
operations acquiring the write lock run in process context
and ipt_do_table itself should be reentrant.
What am I missing?
Regards,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 251 bytes --]
reply other threads:[~2004-01-07 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FFC63D9.70705@hipac.org \
--to=creatix@hipac.org \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.