From: Willy Tarreau <w@1wt.eu>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netdev <netdev@vger.kernel.org>,
Rainer Weikusat <rweikusat@mobileactivedefense.com>,
Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Vladimir Davydov <vdavydov@virtuozzo.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Eric Dumazet <edumazet@google.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: struct pid memory leak
Date: Sun, 24 Jan 2016 03:38:24 +0100 [thread overview]
Message-ID: <20160124023824.GA13942@1wt.eu> (raw)
In-Reply-To: <20160124021145.GA12367@1wt.eu>
On Sun, Jan 24, 2016 at 03:11:45AM +0100, Willy Tarreau wrote:
> It doesn't report this on 3.10.
To be more precise, kmemleak reports the issue on 3.13 and not on 3.12.
I'm not sure if it's reliable enough to run a bisect though.
Willy
next prev parent reply other threads:[~2016-01-24 2:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 15:08 struct pid memory leak Dmitry Vyukov
2016-01-22 16:50 ` Eric Dumazet
2016-01-23 18:00 ` Willy Tarreau
2016-01-23 18:14 ` Dmitry Vyukov
2016-01-23 18:40 ` Willy Tarreau
2016-01-23 18:46 ` Dmitry Vyukov
2016-01-23 19:50 ` Eric Dumazet
2016-01-24 2:11 ` Willy Tarreau
2016-01-24 2:38 ` Willy Tarreau [this message]
2016-01-24 2:50 ` Eric Dumazet
2016-01-24 3:04 ` Willy Tarreau
2016-01-24 21:11 ` Eric Dumazet
2016-01-24 21:53 ` [PATCH net] af_unix: fix " Eric Dumazet
2016-01-25 1:06 ` Willy Tarreau
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=20160124023824.GA13942@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rweikusat@mobileactivedefense.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=vdavydov@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.