From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: yjwei@cn.fujitsu.com, davem@davemloft.net
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] IPv6: Fix kernel panic while send SCTP data with IP fragments
Date: Mon, 20 Aug 2007 11:29:15 +0900 (JST) [thread overview]
Message-ID: <20070820.112915.45451796.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <46C8EE3B.40105@cn.fujitsu.com>
In article <46C8EE3B.40105@cn.fujitsu.com> (at Mon, 20 Aug 2007 09:28:27 +0800), Wei Yongjun <yjwei@cn.fujitsu.com> says:
> If ICMP6 message with "Packet Too Big" is received after send SCTP DATA,
> kernel panic will occur when SCTP DATA is send again.
>
> This is because of a bad dest address when call to skb_copy_bits().
:
> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
Acked-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
--yoshfuji
prev parent reply other threads:[~2007-08-20 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 1:28 [PATCH] IPv6: Fix kernel panic while send SCTP data with IP fragments Wei Yongjun
2007-08-20 2:12 ` Arnaldo Carvalho de Melo
2007-08-20 2:27 ` Wei Yongjun
2007-08-21 7:09 ` David Miller
2007-08-20 2:29 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
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=20070820.112915.45451796.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yjwei@cn.fujitsu.com \
/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).