From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7EBF2C04AB5 for ; Thu, 6 Jun 2019 14:19:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5F2F320665 for ; Thu, 6 Jun 2019 14:19:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728814AbfFFOTo (ORCPT ); Thu, 6 Jun 2019 10:19:44 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:51808 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1727961AbfFFOTo (ORCPT ); Thu, 6 Jun 2019 10:19:44 -0400 Received: (qmail 3016 invoked by uid 2102); 6 Jun 2019 10:19:43 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Jun 2019 10:19:43 -0400 Date: Thu, 6 Jun 2019 10:19:43 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Andrea Parri cc: "Paul E. McKenney" , Boqun Feng , Herbert Xu , Linus Torvalds , Frederic Weisbecker , Fengguang Wu , LKP , LKML , Netdev , "David S. Miller" , Luc Maranget , Jade Alglave Subject: Re: rcu_read_lock lost its compiler barrier In-Reply-To: <20190606081657.GA4249@andrea> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 6 Jun 2019, Andrea Parri wrote: > This seems a sensible change to me: looking forward to seeing a patch, > on top of -rcu/dev, for further review and testing! > > We could also add (to LKMM) the barrier() for rcu_read_{lock,unlock}() > discussed in this thread (maybe once the RCU code and the informal doc > will have settled in such direction). Yes. Also for SRCU. That point had not escaped me. Alan From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8647816408375301056==" MIME-Version: 1.0 From: Alan Stern To: lkp@lists.01.org Subject: Re: rcu_read_lock lost its compiler barrier Date: Thu, 06 Jun 2019 10:19:43 -0400 Message-ID: In-Reply-To: <20190606081657.GA4249@andrea> List-Id: --===============8647816408375301056== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, 6 Jun 2019, Andrea Parri wrote: > This seems a sensible change to me: looking forward to seeing a patch, > on top of -rcu/dev, for further review and testing! > = > We could also add (to LKMM) the barrier() for rcu_read_{lock,unlock}() > discussed in this thread (maybe once the RCU code and the informal doc > will have settled in such direction). Yes. Also for SRCU. That point had not escaped me. Alan --===============8647816408375301056==--