From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com From: Joe Perches In-Reply-To: <20110703192442.GA9504@albatros> References: <20110703111028.GA2862@albatros> <20110703185709.GA7414@albatros> <20110703192442.GA9504@albatros> Content-Type: text/plain; charset="UTF-8" Date: Sun, 03 Jul 2011 12:37:55 -0700 Message-ID: <1309721875.18925.30.camel@Joe-Laptop> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [kernel-hardening] Re: [RFC v1] implement SL*B and stack usercopy runtime checks To: Vasiliy Kulikov Cc: kernel-hardening@lists.openwall.com, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, Arnd Bergmann , Christoph Lameter , Pekka Enberg , Matt Mackall , Andrew Morton , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org List-ID: On Sun, 2011-07-03 at 23:24 +0400, Vasiliy Kulikov wrote: > Btw, if the perfomance will be acceptable, what do you think about > logging/reacting on the spotted overflows? If you do, it might be useful to track the found location(s) and only emit the overflow log entry once as found. Maybe use __builtin_return_address(depth) for tracking.