From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Steffen Klassert <steffen.klassert@secunet.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
David Miller <davem@davemloft.net>,
nicolas.dichtel@6wind.com, Al Viro <viro@zeniv.linux.org.uk>,
Thomas Graf <tgraf@suug.ch>,
xiyou.wangcong@gmail.com, netdev@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
jmorris@namei.org, yoshfuji@linux-ipv6.org,
Patrick McHardy <kaber@trash.net>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Eric Dumazet <edumazet@google.com>,
Kees Cook <keescook@google.com>, Julien Tinnes <jln@google.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: Resource leak in unshare
Date: Mon, 02 Nov 2015 16:03:07 -0800 [thread overview]
Message-ID: <1446508987.23275.35.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <1446494052.23275.25.camel@edumazet-glaptop2.roam.corp.google.com>
On Mon, 2015-11-02 at 11:54 -0800, Eric Dumazet wrote:
> On Mon, 2015-11-02 at 13:01 -0600, Eric W. Biederman wrote:
> > Dmitry Vyukov <dvyukov@google.com> writes:
> >
> > > Hello,
> > >
> > > I am hitting the following warnings on
> > > bcee19f424a0d8c26ecf2607b73c690802658b29 (4.3):
> >
> > Do you have any trace of the earlier failures?
> >
> > This appears to be something caused by an earlier failure (possibly
> > whatever fails to allocate memory). Having network devices present
> > but being in the generic cleanup routines is wrong.
> >
> > If there is no additional information can you please rerun with the
> > following change applied? That should at least report which function is
> > failing, and give us a good clue where to start debugging this.
>
> At first, I would say sit is leaking percpu memory
>
> Load sit module, then :
>
> while :
> do
> ip netns add foo
> ip netns del foo
> done
>
> Will eat all memory eventually.
>
> ipip6_tunnel_init() and ipip6_fb_tunnel_init() are _both_ called for the
> sit0 device, this looks very wrong.
>
>
This memleak might have been added in commit
ebe084aafb7e93adf210e80043c9f69adf56820d
("sit: Use ipip6_tunnel_init as the ndo_init function.")
I'll send a patch asap, if nothing more urgent preempts me today...
next prev parent reply other threads:[~2015-11-03 0:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 11:05 Dmitry Vyukov
2015-11-02 19:01 ` Eric W. Biederman
2015-11-02 19:54 ` Eric Dumazet
2015-11-03 0:03 ` Eric Dumazet [this message]
2015-11-03 1:08 ` Eric Dumazet
2015-11-03 1:16 ` Eric Dumazet
2015-11-03 3:55 ` David Miller
2015-11-03 8:48 ` Dmitry Vyukov
2015-11-03 12:48 ` Eric Dumazet
2015-11-03 15:21 ` Dmitry Vyukov
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=1446508987.23275.35.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=jln@google.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kcc@google.com \
--cc=keescook@google.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=sasha.levin@oracle.com \
--cc=steffen.klassert@secunet.com \
--cc=syzkaller@googlegroups.com \
--cc=tgraf@suug.ch \
--cc=viro@zeniv.linux.org.uk \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.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®