From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Mateusz Guzik <mguzik@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kmemleak splat on copy_process()
Date: Thu, 9 Feb 2017 02:37:32 +0100 [thread overview]
Message-ID: <20170209013732.GL24047@wotan.suse.de> (raw)
In-Reply-To: <20170207080343.GA5065@dhcp22.suse.cz>
On Tue, Feb 07, 2017 at 09:03:43AM +0100, Michal Hocko wrote:
> On Tue 07-02-17 02:37:02, Luis R. Rodriguez wrote:
> > > From a quick check I do not see any leak there either.
> >
> > Then in that case what about:
>
> This just disables the kmemleak altogether which doesn't sound like a
> good idea to me.
Only for this case, but if that is also not desirable let us debug further.
That or I think we could perhaps massage code to make it clearer to kmemleak
things are good.
Luis
next prev parent reply other threads:[~2017-02-09 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 21:06 Luis R. Rodriguez
2017-02-06 9:47 ` Michal Hocko
2017-02-07 1:37 ` Luis R. Rodriguez
2017-02-07 8:03 ` Michal Hocko
2017-02-09 1:37 ` Luis R. Rodriguez [this message]
2017-02-17 17:07 ` Andy Lutomirski
2017-02-17 17:23 ` Luis R. Rodriguez
2017-02-17 19:32 ` Andy Lutomirski
2017-05-15 21:53 ` Luis R. Rodriguez
2017-05-16 6:28 ` Michal Hocko
2017-05-16 13:39 ` Catalin Marinas
2017-05-16 23:55 ` Andy Lutomirski
2017-05-17 11:09 ` Catalin Marinas
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=20170209013732.GL24047@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mguzik@redhat.com \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.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
Powered by JetHome