From: Patrick McHardy <kaber@trash.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
netdev <netdev@vger.kernel.org>, Eric Leblond <eric@regit.org>
Subject: Re: [PATCH next] netfilter: nfqueue: batch verdict support
Date: Tue, 19 Jul 2011 11:45:24 +0200 [thread overview]
Message-ID: <4E255234.3060408@trash.net> (raw)
In-Reply-To: <1309688655.2523.16.camel@edumazet-laptop>
On 03.07.2011 12:24, Eric Dumazet wrote:
> The real question hidden here is : "Should packet ids be monotonic" in
> current implementation and all future ones ?
>
> Before we accept this patch, we should make sure packets id are
> monotonic, and I am afraid its not the case right now.
>
> I suggest following patch then.
>
> [PATCH] netfilter: nfqueue: assert monotonic packet ids
>
> Packet identifier is currently setup in nfqnl_build_packet_message(),
> using one atomic_inc_return().
>
> Problem is that since several cpus might concurrently call
> nfqnl_enqueue_packet() for the same queue, we can deliver packets to
> consumer in non monotonic way (packet N+1 being delivered after packet
> N)
>
> This patch moves the packet id setup from nfqnl_build_packet_message()
> to nfqnl_enqueue_packet() to guarantee correct delivery order.
>
> This also removes one atomic operation.
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> CC: Florian Westphal <fw@strlen.de>
> CC: Pablo Neira Ayuso <pablo@netfilter.org>
> CC: Eric Leblond <eric@regit.org>
Applied, thanks Eric.
next prev parent reply other threads:[~2011-07-19 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 22:14 [PATCH next] netfilter: nfqueue: batch verdict support Florian Westphal
2011-07-03 10:24 ` Eric Dumazet
2011-07-03 19:23 ` Florian Westphal
2011-07-19 9:45 ` Patrick McHardy [this message]
2011-07-05 13:26 ` Patrick McHardy
2011-07-05 15:52 ` Florian Westphal
2011-07-07 13:45 ` Florian Westphal
2011-07-11 9:44 ` Patrick McHardy
2011-07-18 14:10 ` Patrick McHardy
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=4E255234.3060408@trash.net \
--to=kaber@trash.net \
--cc=eric.dumazet@gmail.com \
--cc=eric@regit.org \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).