[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1355491565.10504.7.camel@edumazet-glaptop>
Date: Fri, 14 Dec 2012 05:26:05 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Christoph Paasch <christoph.paasch@...ouvain.be>
Cc: David Miller <davem@...emloft.net>,
Gerrit Renker <gerrit@....abdn.ac.uk>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>, netdev@...r.kernel.org,
dccp@...r.kernel.org
Subject: Re: [PATCH] Fix: kmemleak in tcp_v4/6_syn_recv_sock and
dccp_v4/6_request_recv_sock
On Fri, 2012-12-14 at 08:59 +0100, Christoph Paasch wrote:
> Hi Eric,
>
> On Thursday 13 December 2012 15:38:10 Eric Dumazet wrote:
> > Are you sure the above commit is the bug origin ?
> >
> > It looks like bug was bring by transparent proxy in 2.6.37
> >
> > commit 093d282321daeb19c107e5f1f16d7f68484f3ade
> > Author: Balazs Scheidler <bazsi@...abit.hu>
> > Date: Thu Oct 21 13:06:43 2010 +0200
>
> yes, you are right.
>
> My patch would not easily apply on kernels < 3.0, as it depends on the
> "put_and_exit"-goto.
> Should I send a separate patch? And to whom? (I don't find any guidelines
> about how to submit patches to older stable kernels)
>
Please correct the changelog to include the right commit, so that we can
backport it to needed kernels later. This backport could be done by you
or someone else, don't worry. First step is to get the first patch in
current Linus tree, but with exact information in changelog.
Thanks
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists