From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752026AbcBZCFD (ORCPT ); Thu, 25 Feb 2016 21:05:03 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41042 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751219AbcBZCFB (ORCPT ); Thu, 25 Feb 2016 21:05:01 -0500 Subject: Re: [RFC][PATCH v3 0/2] mm/page_poison.c: Allow for zero poisoning To: Kees Cook , Laura Abbott References: <1456356923-5164-1-git-send-email-keescook@chromium.org> Cc: Andrew Morton , "Kirill A. Shutemov" , Vlastimil Babka , Michal Hocko , Mathias Krause , Dave Hansen , Jianyu Zhan , linux-mm@kvack.org, linux-kernel@vger.kernel.org From: Laura Abbott Message-ID: <56CFB2C9.7070204@redhat.com> Date: Thu, 25 Feb 2016 18:04:57 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <1456356923-5164-1-git-send-email-keescook@chromium.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/24/2016 03:35 PM, Kees Cook wrote: > 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 > The rebase looks fine to me. Were there any more comments on this?