Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E95BBC64ED6 for ; Mon, 27 Feb 2023 16:16:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230064AbjB0QQf (ORCPT ); Mon, 27 Feb 2023 11:16:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60468 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230099AbjB0QQc (ORCPT ); Mon, 27 Feb 2023 11:16:32 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4847F23328; Mon, 27 Feb 2023 08:16:30 -0800 (PST) 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 dfw.source.kernel.org (Postfix) with ESMTPS id BD42460EA7; Mon, 27 Feb 2023 16:16:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BE044C433D2; Mon, 27 Feb 2023 16:16:27 +0000 (UTC) Date: Mon, 27 Feb 2023 11:16:26 -0500 From: Steven Rostedt To: Zhouyi Zhou Cc: Joel Fernandes , Sanan Hasanov , paulmck@kernel.org, frederic@kernel.org, quic_neeraju@quicinc.com, josh@joshtriplett.org, mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com, rcu@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller@googlegroups.com, contact@pgazz.com Subject: Re: BUG: unable to handle kernel NULL pointer dereference in rcu_core Message-ID: <20230227111626.463b8f85@gandalf.local.home> In-Reply-To: References: <20230227103257.4b99b6fb@gandalf.local.home> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 28 Feb 2023 00:11:51 +0800 Zhouyi Zhou wrote: > > Yes certainly, the rcu_head is allocated on the caller side so it > > could have been trampled while the callback was still in flight. > Thank you all for your guidance, I learned a lot during this process > > > > > OR it could be a bug with RCU if the synchronize_rcu() ended before the > > > grace periods have finished. > Thanks again. > > By the way, the syzkaller on my local machine has been running for 8 > hours, only three bugs reported[1][2][3], but they don't seem to be > related to Sanan's original report. > Maybe there are some configuration mismatches between us.The test > continues, I will report to you once I have any new discovery. Note, the above races (either bug, the one that tramples on something in RCU flight, or a synchronize_sched() returning early) may be extremely hard to hit. It could have been the planets were lined up just right to hit the bug, and won't happen for another 27,000 years. -- Steve