From: Simon Horman <horms@verge.net.au>
To: Julian Anastasov <ja@ssi.bg>
Cc: Calvin Owens <calvinowens@fb.com>,
Wensong Zhang <wensong@linux-vs.org>,
lvs-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, agartrell@fb.com, kernel-team@fb.com
Subject: Re: [PATCH] ipvs: Keep skb->sk when allocating headroom on tunnel xmit
Date: Wed, 12 Nov 2014 11:22:16 +0900 [thread overview]
Message-ID: <20141112022214.GE11597@verge.net.au> (raw)
In-Reply-To: <alpine.LFD.2.11.1411080814300.2081@ja.home.ssi.bg>
On Sat, Nov 08, 2014 at 08:16:58AM +0200, Julian Anastasov wrote:
>
> Hello,
>
> On Fri, 7 Nov 2014, Calvin Owens wrote:
>
> > On 11/05/2014 01:21 AM, Julian Anastasov wrote:
> > >
> > > Hello,
> > >
> > > On Tue, 4 Nov 2014, Calvin Owens wrote:
> > >
> > > > ip_vs_prepare_tunneled_skb() ignores ->sk when allocating a new
> > > > skb, either unconditionally setting ->sk to NULL or allowing
> > > > the uninitialized ->sk from a newly allocated skb to leak through
> > > > to the caller.
> > > >
> > > > This patch properly copies ->sk and increments its reference count.
> > > >
> > > > Signed-off-by: Calvin Owens <calvinowens@fb.com>
> > >
> > > Good catch. Please, extend your patch to
> > > fix also the second place that has such error,
> > > ip_vs_tunnel_xmit_v6. This call is missing from long time,
> > > it was not needed. But commits that allow skb->sk (local
> > > clients) already need it, eg.
> >
> > I'm not sure where exactly you mean: ip_vs_tunnel_xmit_v6() calls
> > ip_vs_prepare_tunneled_skb() to do the allocation, so this patch covers that
> > case.
> >
> > In older versions of the kernel, ip_vs_tunnel_xmit_v6() does it directly,
> > could that be what you're looking at?
>
> Sorry, it seems I was checking old branch.
>
> Simon, please apply.
>
> Acked-by: Julian Anastasov <ja@ssi.bg>
Thanks, done.
> > > - f2428ed5e7bc89c7 ("ipvs: load balance ipv6 connections from a local
> > > process"), 2.6.28
> > > - 4856c84c1358b798 ("ipvs: load balance IPv4 connections from a local
> > > process"), 2.6.28
> > >
> > > > ---
> > > > net/netfilter/ipvs/ip_vs_xmit.c | 2 ++
> > > > 1 file changed, 2 insertions(+)
> > > >
> > > > diff --git a/net/netfilter/ipvs/ip_vs_xmit.c
> > > > b/net/netfilter/ipvs/ip_vs_xmit.c
> > > > index 437a366..bd90bf8 100644
> > > > --- a/net/netfilter/ipvs/ip_vs_xmit.c
> > > > +++ b/net/netfilter/ipvs/ip_vs_xmit.c
> > > > @@ -846,6 +846,8 @@ ip_vs_prepare_tunneled_skb(struct sk_buff *skb, int
> > > > skb_af,
> > > > new_skb = skb_realloc_headroom(skb, max_headroom);
> > > > if (!new_skb)
> > > > goto error;
> > > > + if (skb->sk)
> > > > + skb_set_owner_w(new_skb, skb->sk);
> > > > consume_skb(skb);
> > > > skb = new_skb;
> > > > }
>
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
>
prev parent reply other threads:[~2014-11-12 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 0:37 Calvin Owens
2014-11-05 9:21 ` Julian Anastasov
2014-11-07 22:12 ` Calvin Owens
2014-11-08 6:16 ` Julian Anastasov
2014-11-12 2:22 ` Simon Horman [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=20141112022214.GE11597@verge.net.au \
--to=horms@verge.net.au \
--cc=agartrell@fb.com \
--cc=calvinowens@fb.com \
--cc=ja@ssi.bg \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wensong@linux-vs.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
all inboxes | Powered by JetHome®