From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754790AbaKXTHQ (ORCPT ); Mon, 24 Nov 2014 14:07:16 -0500 Received: from e06smtp11.uk.ibm.com ([195.75.94.107]:53351 "EHLO e06smtp11.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754753AbaKXTHL (ORCPT ); Mon, 24 Nov 2014 14:07:11 -0500 Message-ID: <547381D7.2070404@de.ibm.com> Date: Mon, 24 Nov 2014 20:07:03 +0100 From: Christian Borntraeger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Linus Torvalds , Alexei Starovoitov CC: David Howells , "linux-kernel@vger.kernel.org" , "linux-arch@vger.kernel.org" , linux-mips , linux-x86_64@vger.kernel.org, linux-s390 , Paolo Bonzini , Paul McKenney , Ingo Molnar , Catalin Marinas , Will Deacon Subject: Re: [PATCH/RFC 7/7] kernel: Force ACCESS_ONCE to work only on scalar types References: <1416834210-61738-1-git-send-email-borntraeger@de.ibm.com> <1416834210-61738-8-git-send-email-borntraeger@de.ibm.com> <15567.1416835858@warthog.procyon.org.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14112419-0005-0000-0000-00000234AEA0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 24.11.2014 um 19:35 schrieb Linus Torvalds: > On Mon, Nov 24, 2014 at 10:02 AM, Alexei Starovoitov > wrote: >> >> If the goal is to catch non-scalar users, the following is shorter: >> #define ACCESS_ONCE(x) (((typeof(x))0) + *(volatile typeof(x) *)&(x)) > > Me likey. It probably works well in practice, although I think > > - the "(typeof(x))0)" seems unnecessary and wrong. Why not just "0"? > The typeof is not just longer, but it is incorrect for pointer types > (you can add 0 to a pointer, but you cannot add two pointers together) > > - it does mean that the resulting type ends up being upgraded to > "int", for the usual C type reasons. > > Note that the "upgraded to 'int'" is true with or without the > "(typeof(x))0". If you add two 'char' values, the addition is still > done in 'int'. > > Maybe you *meant* that typeof to fix the second problem, like so: > > (typeof(x)) (0 + *(volatile typeof(x) *)&(x)) > > Hmm? That casts the result of the addition, not the zero. Looks really nice, but does not work with ACCESS_ONCE is on the left-hand side: include/linux/rculist.h: In function 'hlist_add_before_rcu': ./arch/x86/include/asm/barrier.h:127:18: error: lvalue required as left operand of assignment ACCESS_ONCE(*p) = (v); \ Alexei's variant is also broken: include/linux/cgroup.h: In function 'task_css': include/linux/compiler.h:381:40: error: invalid operands to binary + (have 'struct css_set *' and 'struct css_set * volatile') #define ACCESS_ONCE(x) (((typeof(x))0) + *(volatile typeof(x) *)&(x)) Anyone with a new propopal? ;-) ^ Christian