From: ebiederm@xmission.com (Eric W. Biederman)
To: "Levin\, Alexander \(Sasha Levin\)" <alexander.levin@verizon.com>
Cc: Michal Hocko <mhocko@kernel.org>,
"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] mm: kill kmemcheck again
Date: Wed, 27 Sep 2017 12:36:27 -0500 [thread overview]
Message-ID: <878th0vyas.fsf@xmission.com> (raw)
In-Reply-To: <20170927152445.pe5ah3hq5hwup75z@sasha-lappy> (Alexander Levin's message of "Wed, 27 Sep 2017 15:24:48 +0000")
"Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com> writes:
> On Wed, Sep 27, 2017 at 05:02:07PM +0200, Michal Hocko wrote:
>>This is just too large to review manually. How have you generated the
>>patch?
>
> Manualy. Note that most of it (~95%) is the result of 'rm arch/x86/mm/kmemcheck'.
>
> Otherwise, I just removed all uses of __GFP_NOWARN/SLAB_NOWARN, and calls to
> various annotations throughout the code.
Do you mean GFP_NOTRACK? GFP_NOWARN has a different meaning.
> I'm not sure about i386 breakage, will take a look, doesn't seem to be too obvious.
Eric
next prev parent reply other threads:[~2017-09-27 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 11:27 [PATCH] mm: kill kmemcheck again Levin, Alexander (Sasha Levin)
2017-09-27 11:32 ` Levin, Alexander (Sasha Levin)
2017-09-27 15:02 ` Michal Hocko
2017-09-27 15:24 ` Levin, Alexander (Sasha Levin)
2017-09-27 17:36 ` Eric W. Biederman [this message]
2017-09-27 22:01 ` Levin, Alexander (Sasha Levin)
2017-09-30 9:48 ` Steven Rostedt
2017-09-30 13:57 ` Vegard Nossum
2017-09-30 20:02 ` Levin, Alexander (Sasha Levin)
2017-10-02 7:29 ` Michal Hocko
2017-10-03 21:02 ` Steven Rostedt
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=878th0vyas.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=rostedt@goodmis.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