[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1456356923-5164-1-git-send-email-keescook@chromium.org>
Date: Wed, 24 Feb 2016 15:35:21 -0800
From: Kees Cook <keescook@...omium.org>
To: Laura Abbott <labbott@...oraproject.org>
Cc: Kees Cook <keescook@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Vlastimil Babka <vbabka@...e.cz>,
Michal Hocko <mhocko@...e.com>,
Mathias Krause <minipli@...glemail.com>,
Dave Hansen <dave.hansen@...el.com>,
Jianyu Zhan <nasa4836@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: [RFC][PATCH v3 0/2] mm/page_poison.c: Allow for zero poisoning
This is my attempt to rebase this series:
[PATCHv2, 2/2] mm/page_poisoning.c: Allow for zero poisoning
[PATCHv2, 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option
to the poisoning series in linux-next. It replaces the following mmotm:
mm-page_poisoningc-allow-for-zero-poisoning.patch
mm-page_poisoningc-allow-for-zero-poisoning-checkpatch-fixes.patch
mm-page_poisonc-enable-page_poisoning-as-a-separate-option.patch
mm-page_poisonc-enable-page_poisoning-as-a-separate-option-fix.patch
These patches work for me (linux-next does not) when using
CONFIG_PAGE_POISONING_ZERO=y
I've marked this RFC because I did the rebase -- bugs should be blamed
on me. :)
-Kees
Powered by blists - more mailing lists