On 1/10/2019 12:05 PM, wenxu wrote:
> On 1/10/2019 12:41 AM, Pablo Neira Ayuso wrote:
>> On Fri, Dec 21, 2018 at 06:12:24PM +0800, we...@ucloud.cn wrote:
>> [...]
>>> +static struct xt_match tunnel_mt_reg __read_mostly = {
>>> + .name = "tunnel",
>>> + .revision = 0,
>>> + .
On 1/10/2019 12:41 AM, Pablo Neira Ayuso wrote:
> On Fri, Dec 21, 2018 at 06:12:24PM +0800, we...@ucloud.cn wrote:
> [...]
>> +static struct xt_match tunnel_mt_reg __read_mostly = {
>> +.name = "tunnel",
>> +.revision = 0,
>> +.family = NFPROTO_UNSPEC,
>> +
On Fri, Dec 21, 2018 at 06:12:24PM +0800, we...@ucloud.cn wrote:
[...]
> +static struct xt_match tunnel_mt_reg __read_mostly = {
> + .name = "tunnel",
> + .revision = 0,
> + .family = NFPROTO_UNSPEC,
> + .match = tunnel_mt,
> + .matchsize =
Hi pablo,
How about the state for this patch?
On 12/21/2018 6:12 PM, we...@ucloud.cn wrote:
> From: wenxu
>
> This patch allows us to match on the tunnel metadata that is available
> of the packet. We can use this to validate if the packet comes from/goes
> to tunnel and the corresponding tunne
From: wenxu
This patch allows us to match on the tunnel metadata that is available
of the packet. We can use this to validate if the packet comes from/goes
to tunnel and the corresponding tunnel ID in the iptables.
Signed-off-by: wenxu
---
include/uapi/linux/netfilter/xt_tunnel.h | 13 +++
On Fri, Nov 11, 2016 at 01:32:38PM +0100, Julia Lawall wrote:
> Since commit 7926dbfa4bc1 ("netfilter: don't use
> mutex_lock_interruptible()"), the function xt_find_table_lock can only
> return NULL on an error. Simplify the call sites and update the
> comment before the function.
Applied, thank
Since commit 7926dbfa4bc1 ("netfilter: don't use
mutex_lock_interruptible()"), the function xt_find_table_lock can only
return NULL on an error. Simplify the call sites and update the
comment before the function.
The semantic patch that change the code is as follows:
(http://coccinelle.lip6.fr/)
Hello.
On 7/24/2016 5:31 AM, Tetsuo Handa wrote:
kmemcheck complains that some of struct nf_hook_ops members allocated at
xt_hook_ops_alloc() are not initialized before nf_register_net_hook() is
called. Add __GFP_ZERO to initialize explicitly.
[ 367.411936] nf_conntrack version 0.5.0 (6144 bu
kmemcheck complains that some of struct nf_hook_ops members allocated at
xt_hook_ops_alloc() are not initialized before nf_register_net_hook() is
called. Add __GFP_ZERO to initialize explicitly.
[ 367.411936] nf_conntrack version 0.5.0 (6144 buckets, 24576 max)
[ 367.458540] ip_tables: (C) 2000-
From: Harald Welte <[EMAIL PROTECTED]>
Date: Thu, 12 Jan 2006 21:47:34 +0100
> Finally, I included all the suggestions/comments for x_tables "take 5",
> ran the nfsim testsuite and feel confident that this is ready for prime
> time.
>
> Please apply this huge one for 2.6.16,
It's been in my tree
10 matches
Mail list logo