Received: by 2002:a25:d80d:0:0:0:0:0 with SMTP id p13csp88120ybg; Sat, 23 May 2020 08:10:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwTHV5X1yjdjIFsOg7yR8MXf3iyAJH0PPYbiQQsi45TbbaolhDG7H1ZhS75lkLDoFaY8YQ0 X-Received: by 2002:a17:906:1c10:: with SMTP id k16mr11795160ejg.511.1590246652748; Sat, 23 May 2020 08:10:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590246652; cv=none; d=google.com; s=arc-20160816; b=YX9F9ThEa6AQtahjtIp0w5TB88/VL+KFDENSvDFHIrBPGh7C81QzDCcG06T6hmj1v3 fQMsqyFooqudjAuDrDn43gxTTiVMLTR3ne7YCCf/6Yszm6DSTD6Tmy39/6nyD5MOTJmU jrvhVCaklzYFyUPYBswCopYJz4oCIAH2VJ9OA1S9CHCcHjPTAYeJCaDGeNJbtg/SOc0f btTDXgtnZj6/6Pho1dldLfIjbqF3qFkFQ3sl6sumuvbmY7DAu8Vp7Xafxl5jWcuY5isy EeYeuAdNYud603Oj9YNils5/STPebETqnYkxoDrtLEv5h8HO8jVmZWUGoRfAfi0Gk4ad hteQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=6C032i4ZLRw5BmUERsLfimtZ9ZEAhnnHEfDMEzaK0MQ=; b=PBAnGfdBme5dUndhVBZNVeqRaDku16g42vqKGzv0pCND1f1h8xTgROnX/kcavZCKLr InphBs6nPeCtBHgUwHi3Qpnylpk4mqb+c3Rt5EFM/qC8siQUz9CoNYhLkfHTJFqXYMXT QFMatv+J4aZgasix+VRYc+uM5zjvR+tY7Lk5zF2E/s1jlXlLkklcBn9k1t5fsOXd6LtE oQr9IEHSArULa2pyG/Hh2vZnB9zWNOAKEKMcgsO0bNzzODXxw+Oou72l8cAyN2IjShB5 E1Vw6hAh0SkMg2ohaF0rShYbasnrlk3BUBEl/jjwnnl/251VxRCAs5Bj5TiQ10rJcDLw HPbA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d17si6225137ejh.334.2020.05.23.08.10.28; Sat, 23 May 2020 08:10:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387903AbgEWPIm (ORCPT + 99 others); Sat, 23 May 2020 11:08:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57096 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387815AbgEWPIm (ORCPT ); Sat, 23 May 2020 11:08:42 -0400 Received: from Galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D5E65C061A0E; Sat, 23 May 2020 08:08:41 -0700 (PDT) Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1jcVlH-0002Qs-UX; Sat, 23 May 2020 17:08:31 +0200 Date: Sat, 23 May 2020 17:08:31 +0200 From: Sebastian Andrzej Siewior To: "Paul E. McKenney" Cc: Peter Zijlstra , linux-kernel@vger.kernel.org, Ingo Molnar , Steven Rostedt , Will Deacon , Thomas Gleixner , Linus Torvalds , Lai Jiangshan , Josh Triplett , Mathieu Desnoyers , rcu@vger.kernel.org Subject: Re: [PATCH 3/8] srcu: Use local_lock() for per-CPU struct srcu_data access Message-ID: <20200523150831.wdrthklakwm6wago@linutronix.de> References: <20200519201912.1564477-1-bigeasy@linutronix.de> <20200519201912.1564477-4-bigeasy@linutronix.de> <20200520102407.GF317569@hirez.programming.kicks-ass.net> <20200520120608.mwros5jurmidxxfv@linutronix.de> <20200520184345.GU2869@paulmck-ThinkPad-P72> <20200522151255.rtqnuk2cl3dpruou@linutronix.de> <20200522173953.GI2869@paulmck-ThinkPad-P72> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200522173953.GI2869@paulmck-ThinkPad-P72> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-05-22 10:39:53 [-0700], Paul E. McKenney wrote: > It looks good to me, but I have not yet tested it. (Happy to let you > take the first crack at rcutorture in any case, scenarios SRCU-P and > SRCU-N.) on it. > > That check_init_srcu_struct() is needed, because otherwise: > > > > | BUG: spinlock bad magic on CPU#2, swapper/0/1 > > | lock: 0xffff88803ed28ac0, .magic: 00000000, .owner: /-1, .owner_cpu: 0 > > | CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.7.0-rc6+ #81 > > | Call Trace: > > | dump_stack+0x71/0xa0 > > | do_raw_spin_lock+0x6c/0xb0 > > | _raw_spin_lock_irqsave+0x33/0x40 > > | synchronize_srcu+0x24/0xc9 > > | wakeup_source_remove+0x4d/0x70 > > | wakeup_source_unregister.part.0+0x9/0x40 > > | device_wakeup_enable+0x99/0xc0 > > > > I'm not sure if there should be an explicit init of `wakeup_srcu' or if > > an srcu function (like call_srcu()) is supposed to do it. > > It is fine. Beforehand, that check_init_srcu_struct() would have been > invoked very shortly thereafter from __call_srcu(), and there is no > instead harm invoking it a few microseconds earlier. ;-) Oki. I wasn't sure if an explizit initialized on wakeup_srcu's side was missing or if this is new since we use the lock earlier. > Thanx, Paul Sebastian