From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f72.google.com (mail-pg0-f72.google.com [74.125.83.72]) by kanga.kvack.org (Postfix) with ESMTP id C573A6B0314 for ; Fri, 16 Jun 2017 11:53:04 -0400 (EDT) Received: by mail-pg0-f72.google.com with SMTP id k68so45289542pgc.13 for ; Fri, 16 Jun 2017 08:53:04 -0700 (PDT) Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40116.outbound.protection.outlook.com. [40.107.4.116]) by mx.google.com with ESMTPS id h66si2344343pfe.357.2017.06.16.08.53.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 16 Jun 2017 08:53:04 -0700 (PDT) Subject: Re: [PATCH v3 5/7] kasan: allow kasan_check_read/write() to accept pointers to volatiles References: From: Andrey Ryabinin Message-ID: Date: Fri, 16 Jun 2017 18:54:49 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Dmitry Vyukov , mark.rutland@arm.com, peterz@infradead.org, mingo@redhat.com, will.deacon@arm.com, hpa@zytor.com Cc: Thomas Gleixner , Andrew Morton , linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org, kasan-dev@googlegroups.com On 06/06/2017 01:11 PM, Dmitry Vyukov wrote: > Currently kasan_check_read/write() accept 'const void*', make them > accept 'const volatile void*'. This is required for instrumentation > of atomic operations and there is just no reason to not allow that. > > Signed-off-by: Dmitry Vyukov > Cc: Mark Rutland > Cc: Andrey Ryabinin > Cc: Thomas Gleixner > Cc: "H. Peter Anvin" > Cc: Peter Zijlstra > Cc: Andrew Morton > Cc: linux-kernel@vger.kernel.org > Cc: x86@kernel.org > Cc: linux-mm@kvack.org > Cc: kasan-dev@googlegroups.com Reviewed-by: Andrey Ryabinin -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org