From: Patrick McHardy <kaber@trash.net>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: David Miller <davem@davemloft.net>,
yasuyuki.kozakai@toshiba.co.jp, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] IPv6: conntrack: Use protocol-related initialization routine to initial queues of IPv6 connection track
Date: Tue, 26 Jan 2010 13:46:46 +0100 [thread overview]
Message-ID: <4B5EE436.3040204@trash.net> (raw)
In-Reply-To: <4B5EE2C6.6010802@cn.fujitsu.com>
Shan Wei wrote:
> David Miller wrote, at 01/26/2010 03:32 PM:
>> From: Shan Wei <shanwei@cn.fujitsu.com>
>> Date: Tue, 26 Jan 2010 10:31:10 +0800
>>
>>> IPv6 connection track and IPv6 stack separately use a different queue to
>>> manage received fragments. The former uses nf_ct_frag6_queue structure,
>>> the latter uses frag_queue structure.
>>>
>>> When creating new queue for IPv6 connection track, ip6_frag_init()
>>> that belongs to IPv6 stack is called to initial nf_ct_frag6_queue structure.
>>> This broken the saddr&daddr member in nf_ct_frag6_queue, and then hash value
>>> generated by nf_hashfn() is not equal with that generated by fq_find().
>>> So, a new received fragment can't be inserted to right queue.
>>>
>>> The patch fixes the bug with protocol-related initialization routine.
>>> The patch-set have been tested.
>>>
>>> Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
>> This breakage was recently introduced by:
>>
>> commit 0b5ccb2ee250136dd7385b1c7da28417d0d4d32d
>> Author: Patrick McHardy <kaber@trash.net>
>> Date: Tue Dec 15 16:59:18 2009 +0100
>>
>> ipv6: reassembly: use seperate reassembly queues for conntrack and local delivery
>
> Yes, this patch adds user member to frag_queue structure,but not to nf_ct_frag6_queue structure.
Oops, sorry. Not sure why I missed this, I've successfully
tested that change multiple times.
> Please ignore the patch-set.
> Can you apply the following patch(bug-fix) to your net-tree?
>
> --
> [PATCH]IPv6: conntrack: Add member of user to nf_ct_frag6_queue structure
>
> The commit 0b5ccb2(title:ipv6: reassembly: use seperate reassembly queues for
> conntrack and local delivery) has broken the saddr&&daddr member of
> nf_ct_frag6_queue when creating new queue. And then hash value
> generated by nf_hashfn() was not equal with that generated by fq_find().
> So, a new received fragment can't be inserted to right queue.
>
> The patch fixes the bug with adding member of user to nf_ct_frag6_queue structure.
>
> Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
Acked-by: Patrick McHardy <kaber@trash.net>
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-26 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 2:31 [PATCH 1/2] IPv6: conntrack: Use protocol-related initialization routine to initial queues of IPv6 connection track Shan Wei
2010-01-26 7:32 ` David Miller
2010-01-26 12:40 ` Shan Wei
2010-01-26 12:46 ` Patrick McHardy [this message]
2010-01-26 13:11 ` David Miller
2010-01-26 15:46 ` Patrick McHardy
2010-10-30 18:41 ` Pascal Hambourg
2010-01-26 12:56 ` Yasuyuki KOZAKAI
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=4B5EE436.3040204@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shanwei@cn.fujitsu.com \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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).