From: Alexander Aring <alex.aring@gmail.com>
To: Fan Du <fan.du@windriver.com>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH/RFC net] ipv6: fix fragmentation bug
Date: Mon, 4 Nov 2013 10:43:04 +0100 [thread overview]
Message-ID: <20131104094303.GA20131@omega> (raw)
In-Reply-To: <52776B5A.6030701@windriver.com>
Hi,
On Mon, Nov 04, 2013 at 05:39:38PM +0800, Fan Du wrote:
> Hi, Alexander
>
> I don't know whether which head commit you are sitting, this issue might has already been fixed by Steffen:
> https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=84502b5ef9849a9694673b15c31bd3ac693010ae
>
>
oh I am using current net-next which haven't this fix.
Thanks
next prev parent reply other threads:[~2013-11-04 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 9:26 [PATCH/RFC net] ipv6: probably fragmentation bug Alexander Aring
2013-11-04 9:26 ` [PATCH/RFC net] ipv6: fix " Alexander Aring
2013-11-04 9:39 ` Fan Du
2013-11-04 9:43 ` Alexander Aring [this message]
2013-11-04 9:46 ` Fan Du
2013-11-04 9:51 ` Alexander Aring
2013-11-04 14:25 ` Eric Dumazet
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=20131104094303.GA20131@omega \
--to=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).