Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp754717iog; Mon, 13 Jun 2022 12:12:26 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vOB+UbTaQY27mGSo2wAro12wfKnWN14CCB9nEc8EEuVN36IRjyIbh86J1BCGNlLtpT+GBG X-Received: by 2002:a17:902:9f8e:b0:163:bda9:ccb1 with SMTP id g14-20020a1709029f8e00b00163bda9ccb1mr438015plq.124.1655147546059; Mon, 13 Jun 2022 12:12:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655147546; cv=none; d=google.com; s=arc-20160816; b=yQjsvb2VKH4FADKrURxcIfYT1hD2xCh+lFcWO3f80/C+QEcUiLpKwtxUHsP7oziZKB 7/8WIYCC+luvPiqgTCE6aJvJFslUW+MLKo1tc/fq+u49l0XkS/Ex3/fcNuf9aXURviqv aS7tnNjA39Wt9zVffpzMdkheWYWCc87UwFkp+rfZYz2+F1iAx7CqXU1BZcnWZN8jrnRs iFOiJTIZwPX0u+KtGqnM38SjckoxS/W/Ssuq/wspErez8n1XUoEArN+3hpP+8j3bmLCr 96cyxn14fXf63rYhkPvfUF7MBPmcCTrFGHTzi21ruM1j28CXPAudQGxeqPQhBbMkoxC7 YAzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=vpPgcmgS/82KB419zhWAZl5f219TPLTXSs4ekS7LcVU=; b=uxxjFvv3qO4ZBpwOzMW9/gQJlYu3vTulyZGRYVrTvvoKyfv8HCUXZhV1CCVX+hmQhq VzIsTymAdz3TXuE9P4iTL5wYxyRJVMeDoGP+mXBKK4tIpvWFohEaCDU2JiDQsvSc0ejt eQ37SVYHxg9YkkElhuxUCtz8f1ICvfk+cDyuHA1rnVg6zdfLcaK/PtPvHNSQakMPFXHF omO1NMIssVyCR4kYjv6No0/FWPvekgicQHeO5movErPbqktebdf6aXbT8L4pdL4zwIC+ O/y0MdK14StPF8Oi62sUeDZpoB6mx0grSZjRXCaPJxWvseokKuMWtbiaqds9WKYBryy7 ZpFw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=cBMJnTuV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b15-20020a65668f000000b003fd8a0059a5si11483791pgw.316.2022.06.13.12.12.13; Mon, 13 Jun 2022 12:12:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=cBMJnTuV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344653AbiFMSmb (ORCPT + 99 others); Mon, 13 Jun 2022 14:42:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49712 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344348AbiFMSl4 (ORCPT ); Mon, 13 Jun 2022 14:41:56 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8CA3A6213B for ; Mon, 13 Jun 2022 08:23:40 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 38424B8107B for ; Mon, 13 Jun 2022 15:23:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E959DC34114; Mon, 13 Jun 2022 15:23:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1655133818; bh=39ORVcKGkww5j3cWfJ59utZuZfgeFZ6xrvdw9pRCMcE=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=cBMJnTuVe/bmjbmsCXZA0+huX5Txb6VRI1fgk7BNdzm9ZkevvY77Y23RQJl/UVigz WK1hNZP5FiUOAd6vk0m1sKQzJxLwlBDCkh7m1i7CNaQIjsr1mtLIpp7z5jbVIbiQIJ friK4tLQoJJZKYF+G7hfdlNl2zPsdEnL7I3Wk3zoHvXq2WkM67Zmb9I7UjxqbpAbJJ qoUD2LMIU8DfSSd0ZkxjRPqjeOf3he5nzpAigRGQWjKM9RUqbppchJ7C1vI4y9airB 7k19KlSqb00T80xU3GCHbTC2jw4AgB0oRTvhaXj7dstJGhAtNHxZfon0KE//cz/LUT IlgzSSw2a7UVA== Received: by paulmck-ThinkPad-P17-Gen-1.home (Postfix, from userid 1000) id 8BD685C0510; Mon, 13 Jun 2022 08:23:37 -0700 (PDT) Date: Mon, 13 Jun 2022 08:23:37 -0700 From: "Paul E. McKenney" To: "Zhang, Qiang1" Cc: "Eric W. Biederman" , syzbot , "brauner@kernel.org" , "keescook@chromium.org" , "linux-kernel@vger.kernel.org" , "syzkaller-bugs@googlegroups.com" Subject: Re: [syzbot] WARNING in exit_tasks_rcu_finish Message-ID: <20220613152337.GD1790663@paulmck-ThinkPad-P17-Gen-1> Reply-To: paulmck@kernel.org References: <000000000000e2fc3f05e141f930@google.com> <87bkux1yn4.fsf@email.froward.int.ebiederm.org> <20220612202204.GX1790663@paulmck-ThinkPad-P17-Gen-1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-8.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 13, 2022 at 01:55:31PM +0000, Zhang, Qiang1 wrote: > > syzbot writes: > > > > > Hello, > > > > > > syzbot found the following issue on: > > > > > > HEAD commit: 6d0c80680317 Add linux-next specific files for 20220610 > > > git tree: linux-next > > > console output: > > > https://syzkaller.appspot.com/x/log.txt?x=13b52c2ff00000 > > > kernel config: > > > https://syzkaller.appspot.com/x/.config?x=a30d6e3e814e5931 > > > dashboard link: https://syzkaller.appspot.com/bug?extid=9bb26e7c5e8e4fa7e641 > > > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > > > > > > Unfortunately, I don't have any reproducer for this issue yet. > > > > I don't understand what is going on in linux-next kernel/rcu/tasks.h > > looks different than in Linus's tree. Paul does that mean you have > > some staged rcu changes? > > >Less than 100 RCU-related patches in -rcu, so not all that bad. ;-) > > > >But yes, this could possibly be an issue in one of those patches. > > > Eric > > > > > > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > > > Reported-by: syzbot+9bb26e7c5e8e4fa7e641@syzkaller.appspotmail.com > > > > > > ------------[ cut here ]------------ > > > WARNING: CPU: 1 PID: 28639 at kernel/rcu/tasks.h:1664 > > > exit_tasks_rcu_finish_trace kernel/rcu/tasks.h:1664 [inline] > > > WARNING: CPU: 1 PID: 28639 at kernel/rcu/tasks.h:1664 > > > exit_tasks_rcu_finish+0x122/0x1b0 kernel/rcu/tasks.h:1006 > > >The usual way for this warning to trigger is for these a task to exit while in an RCU Tasks Trace read-side critical section: > > > > rcu_read_lock_trace(); > > do_something_that_causes_task_exit(); > > > > Hi Paul, wether the following scenarios be considered > > rcu_read_unlock_trace_special > ->if (trs.b.blocked) > ->raw_spin_lock_irqsave_rcu_node > ->list_del_init(&t->trc_blkd_node) > ->WRITE_ONCE(t->trc_reader_special.b.blocked, false) > ->raw_spin_unlock_irqrestore_rcu_node > ->Inerrrupt > ->schedule > ->rcu_note_context_switch > ->rcu_tasks_trace_qs > If (___rttq_nesting && !READ_ONCE((t)->trc_reader_special.b.blocked) > /*___rttq_nesting ==1 && (t)->trc_reader_special.b.blocked =false*/ > rcu_tasks_trace_qs_blkd(t) > ->WRITE_ONCE(t->trc_reader_nesting, 0) > ....... > -> exit_tasks_rcu_finish > > Whether the following patch can fix it, or what am I missing? > Any thoughts? > > diff --git a/kernel/rcu/tasks.h b/kernel/rcu/tasks.h > index f1209ce621c5..c607e4c914d3 100644 > --- a/kernel/rcu/tasks.h > +++ b/kernel/rcu/tasks.h > @@ -1247,6 +1247,7 @@ void rcu_read_unlock_trace_special(struct task_struct *t) > struct rcu_tasks_percpu *rtpcp; > union rcu_special trs; > > + WRITE_ONCE(t->trc_reader_nesting, 0); > // Open-coded full-word version of rcu_ld_need_qs(). > smp_mb(); // Enforce full grace-period ordering. > trs = smp_load_acquire(&t->trc_reader_special); > @@ -1267,7 +1268,6 @@ void rcu_read_unlock_trace_special(struct task_struct *t) > WRITE_ONCE(t->trc_reader_special.b.blocked, false); > raw_spin_unlock_irqrestore_rcu_node(rtpcp, flags); > } > - WRITE_ONCE(t->trc_reader_nesting, 0); > } > EXPORT_SYMBOL_GPL(rcu_read_unlock_trace_special); Thank you for looking into this! You do have what I believe to be the correct failure scenario, but the above fix would break nested RCU Tasks Trace read-side critical sections. But would you be willing to try out the patch shown below? Thanx, Paul ------------------------------------------------------------------------ diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h index 08059d8d4f5a7..937a58b3266bf 100644 --- a/include/linux/rcupdate.h +++ b/include/linux/rcupdate.h @@ -184,7 +184,7 @@ void rcu_tasks_trace_qs_blkd(struct task_struct *t); if (likely(!READ_ONCE((t)->trc_reader_special.b.need_qs)) && \ likely(!___rttq_nesting)) { \ rcu_trc_cmpxchg_need_qs((t), 0, TRC_NEED_QS_CHECKED); \ - } else if (___rttq_nesting && \ + } else if (___rttq_nesting && ___rttq_nesting != INT_MIN && \ !READ_ONCE((t)->trc_reader_special.b.blocked)) { \ rcu_tasks_trace_qs_blkd(t); \ } \ diff --git a/include/linux/rcupdate_trace.h b/include/linux/rcupdate_trace.h index 6f9c358173989..9bc8cbb33340b 100644 --- a/include/linux/rcupdate_trace.h +++ b/include/linux/rcupdate_trace.h @@ -75,7 +75,7 @@ static inline void rcu_read_unlock_trace(void) nesting = READ_ONCE(t->trc_reader_nesting) - 1; barrier(); // Critical section before disabling. // Disable IPI-based setting of .need_qs. - WRITE_ONCE(t->trc_reader_nesting, INT_MIN); + WRITE_ONCE(t->trc_reader_nesting, INT_MIN + nesting); if (likely(!READ_ONCE(t->trc_reader_special.s)) || nesting) { WRITE_ONCE(t->trc_reader_nesting, nesting); return; // We assume shallow reader nesting.