From: Daniel Borkmann <dborkman@redhat.com>
To: netdev@vger.kernel.org, fengguang.wu@intel.com
Cc: "linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Subject: Re: [PATCH net-next] ipv6: move ip6_sk_accept_pmtu from generic pmtu update path to ipv6 one
Date: Thu, 19 Dec 2013 13:57:54 +0100 [thread overview]
Message-ID: <52B2ED52.90604@redhat.com> (raw)
In-Reply-To: <20131219115458.GC14429@order.stressinduktion.org>
On 12/19/2013 12:54 PM, Hannes Frederic Sowa wrote:
> In commit 93b36cf3425b9b ("ipv6: support IPV6_PMTU_INTERFACE on sockets")
> I made a horrible mistake to add ip6_sk_accept_pmtu to the generic
> sctp_icmp_frag_needed path. This results in build warnings if IPv6 is
> disabled which were luckily caught by Fengguang's kbuild bot. But it
> also leads to a kernel panic IPv4 frag-needed packet is received.
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Thanks, also cc'ing linux-sctp.
Fixes: 93b36cf3425b ("ipv6: support IPV6_PMTU_INTERFACE on sockets")
Acked-by: Daniel Borkmann <dborkman@redhat.com>
> ---
> net/sctp/input.c | 3 ---
> net/sctp/ipv6.c | 3 ++-
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/net/sctp/input.c b/net/sctp/input.c
> index 042ec6c..2a192a7 100644
> --- a/net/sctp/input.c
> +++ b/net/sctp/input.c
> @@ -389,9 +389,6 @@ void sctp_icmp_frag_needed(struct sock *sk, struct sctp_association *asoc,
> if (!t || (t->pathmtu <= pmtu))
> return;
>
> - if (!ip6_sk_accept_pmtu(sk))
> - return;
> -
> if (sock_owned_by_user(sk)) {
> asoc->pmtu_pending = 1;
> t->pmtu_pending = 1;
> diff --git a/net/sctp/ipv6.c b/net/sctp/ipv6.c
> index 32db816..00bea3f 100644
> --- a/net/sctp/ipv6.c
> +++ b/net/sctp/ipv6.c
> @@ -172,7 +172,8 @@ static void sctp_v6_err(struct sk_buff *skb, struct inet6_skb_parm *opt,
>
> switch (type) {
> case ICMPV6_PKT_TOOBIG:
> - sctp_icmp_frag_needed(sk, asoc, transport, ntohl(info));
> + if (ip6_sk_accept_pmtu(sk))
> + sctp_icmp_frag_needed(sk, asoc, transport, ntohl(info));
> goto out_unlock;
> case ICMPV6_PARAMPROB:
> if (ICMPV6_UNK_NEXTHDR == code) {
>
prev parent reply other threads:[~2013-12-19 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 11:54 [PATCH net-next] ipv6: move ip6_sk_accept_pmtu from generic pmtu update path to ipv6 one Hannes Frederic Sowa
2013-12-19 12:57 ` Daniel Borkmann [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=52B2ED52.90604@redhat.com \
--to=dborkman@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=hannes@stressinduktion.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.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).