Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp7686804ybi; Wed, 5 Jun 2019 23:16:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqxdC1yQBs4I0n9J84j6Me7Fihsk0/Z1Q6u7HJS1TueyfKRTRd2oHBpNRo63C91zMjjJ75X6 X-Received: by 2002:a17:902:42e2:: with SMTP id h89mr48774991pld.332.1559801785810; Wed, 05 Jun 2019 23:16:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559801785; cv=none; d=google.com; s=arc-20160816; b=yDaKq1SJHKqDK0Dk9N7lOtcFWJa9CKYH94In72sVJFxVLU9nHAmeGCpTPiOcERugl1 2BRRVaY/QedFcAtp7ygbiyfCuDPRERJq2atvETI/6Q1G1J3W+kfMwYMELvxJV9CXUtlO Ybasdexoul4SWpfIHS6ZoCiJ/DLyclwgP5E3eLv0kzKXgJVvqiuEcZEkPQ3xlQkEGvV0 Jx6136FKC2HXqzXZe0SUFtTS0WElq2FYzFu+7v705881w8Adukiev/i8gCYObKTNfYLe 5KlU5gZTczPkJ0epzjAjW3+V50WSkD4F29Npz3B10UKtdONVAdNXKDaB1DiPCz5Gon+f YtqA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=zsS69eOwn0Pnuaw2ApnB0x1i06CBY4tAwmaHizUhhcY=; b=l4V8D3JjDcZIy/yaHbJ0Q4DbIIOpOIOkzeT4F+xOcBXUpjRqQd/VJrKEKmerwJzlAs Uc/pgAKzlL7OSB0hVjCDh0npPf0v+wgPfN6YeaPPYK/c0jnd+MU3g99npxkE7q3Ht2yJ pwG0CiEKz7pKRmRCZWDzgtyBGxV2DE57lVNFl881DlwaAN8ENThWdeQTTfP0LDexHDxl XHmzw/narV5i9RC4S7vyS8QNH1aeN5kwa8Rq78G7PYNeiNT8WZwi8Wpo3UUTMQh1LmVv VRb2yIwIhAvR/+ef6yQqFSOpk6BiCuCOBQlSZyWTs3DxNrPDRwiuICRqMLI1vJ1W1ehx pWaA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a17si1070475pjq.101.2019.06.05.23.16.07; Wed, 05 Jun 2019 23:16:25 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726613AbfFFGOz (ORCPT + 99 others); Thu, 6 Jun 2019 02:14:55 -0400 Received: from helcar.hmeau.com ([216.24.177.18]:36354 "EHLO deadmen.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725267AbfFFGOz (ORCPT ); Thu, 6 Jun 2019 02:14:55 -0400 Received: from gondobar.mordor.me.apana.org.au ([192.168.128.4] helo=gondobar) by deadmen.hmeau.com with esmtps (Exim 4.89 #2 (Debian)) id 1hYlfi-0006IW-UG; Thu, 06 Jun 2019 14:14:47 +0800 Received: from herbert by gondobar with local (Exim 4.89) (envelope-from ) id 1hYlfa-0003iA-FC; Thu, 06 Jun 2019 14:14:38 +0800 Date: Thu, 6 Jun 2019 14:14:38 +0800 From: Herbert Xu To: "Paul E. McKenney" Cc: Alan Stern , Boqun Feng , Linus Torvalds , Frederic Weisbecker , Fengguang Wu , LKP , LKML , Netdev , "David S. Miller" , Andrea Parri , Luc Maranget , Jade Alglave Subject: Re: rcu_read_lock lost its compiler barrier Message-ID: <20190606061438.nyzaeppdbqjt3jbp@gondor.apana.org.au> References: <20190603200301.GM28207@linux.ibm.com> <20190606045109.zjfxxbkzq4wb64bj@gondor.apana.org.au> <20190606060511.GA28207@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190606060511.GA28207@linux.ibm.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 05, 2019 at 11:05:11PM -0700, Paul E. McKenney wrote: > > In case you were wondering, the reason that I was giving you such > a hard time was that from what I could see, you were pushing for no > {READ,WRITE}_ONCE() at all. ;-) Hmm, that's exactly what it should be in net/ipv4/inet_fragment.c. We don't need the READ_ONCE/WRITE_ONCE (or volatile marking) at all. Even if the compiler dices and slices the reads/writes of "a" into a thousand pieces, it should still work if the RCU primitives are worth their salt. But I do concede that in the general RCU case you must have the READ_ONCE/WRITE_ONCE calls for rcu_dereference/rcu_assign_pointer. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt