From: Kees Cook <keescook@chromium.org>
To: Laura Abbott <labbott@fedoraproject.org>
Cc: Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
Mathias Krause <minipli@googlemail.com>,
Dave Hansen <dave.hansen@intel.com>,
Jianyu Zhan <nasa4836@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [RFC][PATCH v3 0/2] mm/page_poison.c: Allow for zero poisoning
Date: Wed, 24 Feb 2016 15:35:21 -0800 [thread overview]
Message-ID: <1456356923-5164-1-git-send-email-keescook@chromium.org> (raw)
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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2016-02-24 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 23:35 Kees Cook [this message]
2016-02-24 23:35 ` [RFC][PATCH v3 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option Kees Cook
2016-02-26 2:53 ` Jianyu Zhan
2016-02-26 4:45 ` Laura Abbott
2016-02-26 5:34 ` Jianyu Zhan
2016-02-26 22:21 ` Laura Abbott
2016-02-24 23:35 ` [RFC][PATCH v3 2/2] mm/page_poison.c: Allow for zero poisoning Kees Cook
2016-02-26 2:04 ` [RFC][PATCH v3 0/2] " Laura Abbott
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=1456356923-5164-1-git-send-email-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=labbott@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minipli@googlemail.com \
--cc=nasa4836@gmail.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).