From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754516AbbJPQFg (ORCPT ); Fri, 16 Oct 2015 12:05:36 -0400 Received: from e36.co.us.ibm.com ([32.97.110.154]:53573 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753777AbbJPQFd (ORCPT ); Fri, 16 Oct 2015 12:05:33 -0400 X-IBM-Helo: d03dlp01.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Fri, 16 Oct 2015 09:05:28 -0700 From: "Paul E. McKenney" To: Borislav Petkov Cc: Andrey Ryabinin , linux-kernel@vger.kernel.org, Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , x86@kernel.org, Andrew Morton , Andy Lutomirski , Andrey Konovalov , Kostya Serebryany , Alexander Potapenko , kasan-dev , Denys Vlasenko , Andi Kleen , Dmitry Vyukov , Sasha Levin , Wolfram Gloger , Peter Zijlstra Subject: Re: [PATCH v4 1/2] compiler, atomics: Provide READ_ONCE_NOKSAN() Message-ID: <20151016160528.GR3910@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <1444739750-29241-1-git-send-email-aryabinin@virtuozzo.com> <1444988694-26043-1-git-send-email-aryabinin@virtuozzo.com> <1444988694-26043-2-git-send-email-aryabinin@virtuozzo.com> <20151016103338.GE31612@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151016103338.GE31612@pd.tnic> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15101616-0021-0000-0000-000013BB8EA5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 16, 2015 at 12:33:38PM +0200, Borislav Petkov wrote: > On Fri, Oct 16, 2015 at 12:44:53PM +0300, Andrey Ryabinin wrote: > > Some code may perform racy by design memory reads. This could be > > harmless, yet such code may produce KASAN warnings. > > > > To hide such accesses from KASAN this patch introduces > > READ_ONCE_NOKSAN() macro. KASAN will not check the memory > > accessed by READ_ONCE_NOKSAN(). The KernelThreadSanitizer (KTSAN) > > is going to ignore it as well. > > Frankly, the "NOKSAN" suffix is too specific. I know, I know, I'm > bikeshedding but what happens if yet another tool wants to be disabled > from checking there and that tool is not *SAN? We rename again? Plaid, I say!!! The color of the bikeshed must be plaid!!! ;-) Thanx, Paul > So the "NOCHECK" suffix made much more sense, even if it was generic. > IMNSVHO. > > Thanks. > > -- > Regards/Gruss, > Boris. > > ECO tip #101: Trim your mails when you reply. >