From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com Date: Fri, 29 Jan 2016 11:45:43 +0100 From: Pavel Machek Message-ID: <20160129104543.GA21224@amd> References: <1454035099-31583-1-git-send-email-labbott@fedoraproject.org> <1454035099-31583-3-git-send-email-labbott@fedoraproject.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1454035099-31583-3-git-send-email-labbott@fedoraproject.org> Subject: [kernel-hardening] Re: [PATCHv2 2/2] mm/page_poisoning.c: Allow for zero poisoning To: Laura Abbott Cc: Andrew Morton , "Kirill A. Shutemov" , Vlastimil Babka , Michal Hocko , "Rafael J. Wysocki" , Len Brown , linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com, Kees Cook , linux-pm@vger.kernel.org List-ID: Hi! > By default, page poisoning uses a poison value (0xaa) on free. If this > is changed to 0, the page is not only sanitized but zeroing on alloc > with __GFP_ZERO can be skipped as well. The tradeoff is that detecting > corruption from the poisoning is harder to detect. This feature also > cannot be used with hibernation since pages are not guaranteed to be > zeroed after hibernation. So... this makes kernel harder to debug for performance advantage...? If so.. how big is the performance advantage? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html