From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755699AbcBXXfa (ORCPT ); Wed, 24 Feb 2016 18:35:30 -0500 Received: from mail-pf0-f174.google.com ([209.85.192.174]:35063 "EHLO mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752706AbcBXXf2 (ORCPT ); Wed, 24 Feb 2016 18:35:28 -0500 From: Kees Cook To: Laura Abbott Cc: Kees Cook , Andrew Morton , "Kirill A. Shutemov" , Vlastimil Babka , Michal Hocko , Mathias Krause , Dave Hansen , Jianyu Zhan , 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 Message-Id: <1456356923-5164-1-git-send-email-keescook@chromium.org> X-Mailer: git-send-email 2.6.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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