From: David Miller <davem@davemloft.net>
To: djduanjiong@gmail.com
Cc: steffen.klassert@secunet.com, netdev@vger.kernel.org
Subject: Re: [PATCH v3] ipv6: Change skb->data before using icmpv6_notify() to propagate redirect
Date: Fri, 14 Dec 2012 13:16:38 -0500 (EST) [thread overview]
Message-ID: <20121214.131638.1339938938384537260.davem@davemloft.net> (raw)
In-Reply-To: <50CB22CF.9010505@gmail.com>
From: Duan Jiong <djduanjiong@gmail.com>
Date: Fri, 14 Dec 2012 20:59:59 +0800
>
> In function ndisc_redirect_rcv(), the skb->data points to the transport
> header, but function icmpv6_notify() need the skb->data points to the
> inner IP packet. So before using icmpv6_notify() to propagate redirect,
> change skb->data to point the inner IP packet that triggered the sending
> of the Redirect, and introduce struct rd_msg to make it easy.
>
> Signed-off-by: Duan Jiong <djduanjiong@gmail.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2012-12-14 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 12:59 [PATCH v3] ipv6: Change skb->data before using icmpv6_notify() to propagate redirect Duan Jiong
2012-12-14 18:16 ` David Miller [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=20121214.131638.1339938938384537260.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=djduanjiong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).