Re: [RFC][PATCH v3 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option

2016-02-26 Thread Laura Abbott
On 02/25/2016 09:34 PM, Jianyu Zhan wrote: On Fri, Feb 26, 2016 at 12:45 PM, Laura Abbott wrote: Do you have some suggestion on wording here? I'm not sure what else to say besides poison patterns to differentiate from hardware poison. Is the below wording OK? config PAGE_POISONING

Re: [RFC][PATCH v3 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option

2016-02-25 Thread Jianyu Zhan
On Fri, Feb 26, 2016 at 12:45 PM, Laura Abbott wrote: > Do you have some suggestion on wording here? I'm not sure what else to > say besides poison patterns to differentiate from hardware poison. > Is the below wording OK? config PAGE_POISONING bool bool "Poison pages after fre

Re: [RFC][PATCH v3 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option

2016-02-25 Thread Laura Abbott
On 02/25/2016 06:53 PM, Jianyu Zhan wrote: On Thu, Feb 25, 2016 at 7:35 AM, Kees Cook wrote: config PAGE_POISONING - bool + bool "Poison pages after freeing" + select PAGE_EXTENSION + select PAGE_POISONING_NO_SANITY if HIBERNATION + ---help--- + Fill the

Re: [RFC][PATCH v3 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option

2016-02-25 Thread Jianyu Zhan
On Thu, Feb 25, 2016 at 7:35 AM, Kees Cook wrote: > config PAGE_POISONING > - bool > + bool "Poison pages after freeing" > + select PAGE_EXTENSION > + select PAGE_POISONING_NO_SANITY if HIBERNATION > + ---help--- > + Fill the pages with poison patterns after

[RFC][PATCH v3 1/2] mm/page_poison.c: Enable PAGE_POISONING as a separate option

2016-02-24 Thread Kees Cook
From: Laura Abbott Page poisoning is currently setup as a feature if architectures don't have architecture debug page_alloc to allow unmapping of pages. It has uses apart from that though. Clearing of the pages on free provides an increase in security as it helps to limit the risk of information