Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1342522
| From | Kees Cook <keescook@chromium.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [RFC][PATCH v3 0/2] mm/page_poison.c: Allow for zero poisoning |
| Date | 2016-02-25 00:40 +0100 |
| Message-ID | <r5Rce-3uS-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
[RFC][PATCH v3 0/2] mm/page_poison.c: Allow for zero poisoning Kees Cook <keescook@chromium.org> - 2016-02-25 00:40 +0100 [RFC][PATCH v3 2/2] mm/page_poison.c: Allow for zero poisoning Kees Cook <keescook@chromium.org> - 2016-02-25 00:40 +0100 Re: [RFC][PATCH v3 0/2] mm/page_poison.c: Allow for zero poisoning Laura Abbott <labbott@redhat.com> - 2016-02-26 03:10 +0100
csiph-web