From: Florian Westphal <fw@strlen.de>
To: Florian Westphal <fw@strlen.de>
Cc: Thadeu Lima de Souza Cascardo <cascardo@redhat.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] skb corruption and kernel panic at forwarding with fragmentation
Date: Thu, 7 Jan 2016 00:49:43 +0100 [thread overview]
Message-ID: <20160106234943.GB23789@breakpoint.cc> (raw)
In-Reply-To: <20160106220334.GA23789@breakpoint.cc>
Florian Westphal <fw@strlen.de> wrote:
> Thadeu Lima de Souza Cascardo <cascardo@redhat.com> wrote:
> > On Wed, Jan 06, 2016 at 11:11:41PM +0300, Konstantin Khlebnikov wrote:
[ skb_gso_segment uses skb->cb[], causes oops if ip_fragment is invoked
on segmented skbs ]
> > I have hit this as well, this fixes it for me on an older kernel. Can you try it
> > on latest kernel?
>
> > diff --git a/net/ipv4/ip_output.c b/net/ipv4/ip_output.c
> > index d8a1745..f44bc91 100644
> > --- a/net/ipv4/ip_output.c
> > +++ b/net/ipv4/ip_output.c
> > @@ -216,6 +216,7 @@ static int ip_finish_output_gso(struct sk_buff *skb)
> > netdev_features_t features;
> > struct sk_buff *segs;
> > int ret = 0;
> > + struct inet_skb_parm ipcb;
> >
> > if (skb_gso_network_seglen(skb) <= ip_skb_dst_mtu(skb))
> > return ip_finish_output2(skb);
> > @@ -227,6 +228,10 @@ static int ip_finish_output_gso(struct sk_buff *skb)
> > * 2) skb arrived via virtio-net, we thus get TSO/GSO skbs directly
> > * from host network stack.
> > */
> > + /* We need to save IPCB here because skb_gso_segment will use
> > + * SKB_GSO_CB.
> > + */
> > + ipcb = *IPCB(skb);
> > features = netif_skb_features(skb);
> > segs = skb_gso_segment(skb, features & ~NETIF_F_GSO_MASK);
> > if (IS_ERR_OR_NULL(segs)) {
> > @@ -241,6 +246,7 @@ static int ip_finish_output_gso(struct sk_buff *skb)
> > int err;
> >
> > segs->next = NULL;
> > + *IPCB(segs) = ipcb;
> > err = ip_fragment(segs, ip_finish_output2);
> >
> > if (err && ret == 0)
>
> I'm worried that this doesn't solve all cases. f.e. xfrm may also
> call skb_gso_segment(), and it will call into ipv4/ipv6 netfilter
> postrouting + ipv4 output functions...
>
> nfqnl_enqueue_packet() is also affected.
... but it seems that those three are the only affected callers
of skb_gso_segment (tbf is ok since skb isn't owned by anyone,
ovs does save/restore already).
I think this patch is the right way, we just need similar
save/restore in nfqnl_enqueue_packet and xfrm_output_gso().
The latter two can be used by either ipv4 or ipv6 so it might
be preferable to just save/restore sizeof(struct skb_gso_cb);
or a union of inet_skb_parm+inet6_skb_parm.
Cascardo, can you cook a patch?
Thanks!
next prev parent reply other threads:[~2016-01-06 23:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 19:15 [BUG] skb corruption and kernel panic at forwarding with fragmentation Konstantin Khlebnikov
2016-01-06 19:59 ` Cong Wang
2016-01-06 20:11 ` Konstantin Khlebnikov
2016-01-06 21:05 ` Thadeu Lima de Souza Cascardo
2016-01-06 22:03 ` Florian Westphal
2016-01-06 23:49 ` Florian Westphal [this message]
2016-01-07 11:00 ` Konstantin Khlebnikov
2016-01-07 11:38 ` Konstantin Khlebnikov
2016-01-07 11:59 ` Eric Dumazet
2016-01-07 12:04 ` Konstantin Khlebnikov
2016-01-07 12:54 ` Eric Dumazet
2016-01-07 19:35 ` Konstantin Khlebnikov
2016-01-07 19:47 ` Eric Dumazet
2016-01-07 12:03 ` Florian Westphal
2016-01-07 18:43 ` [PATCH] net: prevent corruption of skb when using skb_gso_segment Thadeu Lima de Souza Cascardo
2016-01-07 19:31 ` Florian Westphal
2016-01-07 21:16 ` [PATCH v2] " Thadeu Lima de Souza Cascardo
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=20160106234943.GB23789@breakpoint.cc \
--to=fw@strlen.de \
--cc=cascardo@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).