From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2B6BA279324 for ; Fri, 26 Dec 2025 16:51:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=216.40.44.13 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766767906; cv=none; b=LFalwn+imuY4n3XB/m2C1rEZ51fHzKG5jEOycwfmFEPE5hJuJcO7NY8XydiaaqotUPe3Fj6f3L2NU9CergR1ulCwbUZzoA97fo4CSwyFfK4na8BqbkzyZVPugmNqesymiNLMmrLKnwE2FXVrVIRMxl/gqNbD1YQsAPdhM1j0sGI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766767906; c=relaxed/simple; bh=lL4seN95W0lbWaebvAB5SIIF5pWAi64fTKqJ0iGN3A4=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=MrVQPqim3OfIC9VdKrCPCCvBDrHxVH6LJNC3Ctg0i+/kdlL1f6SFNpY43/96ySfKqRPqtgmZI+qIzdMZc4k309JvHulZGZg2nNX2bomZE6mrzgEzqYO40zKkMEUCIm6KgLw8MOn3b7qPNkxZpuHxNjZHtZOHJQxMBH4q/QrJZGU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=goodmis.org; spf=pass smtp.mailfrom=goodmis.org; arc=none smtp.client-ip=216.40.44.13 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=goodmis.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=goodmis.org Received: from omf12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id 02E811A19B1; Fri, 26 Dec 2025 16:51:40 +0000 (UTC) Received: from [HIDDEN] (Authenticated sender: rostedt@goodmis.org) by omf12.hostedemail.com (Postfix) with ESMTPA id 16CDF18; Fri, 26 Dec 2025 16:51:38 +0000 (UTC) Date: Fri, 26 Dec 2025 11:51:36 -0500 From: Steven Rostedt To: "Paul E. McKenney" Cc: Sasha Levin , Theodore Tso , Julia Lawall , Gabriele Paoloni , Kate Stewart , Chuck Wolber , Dmitry Vyukov , Mark Rutland , Thomas Gleixner , Lorenzo Stoakes , Shuah Khan , Chris Mason , linux-kernel@vger.kernel.org Subject: Re: Follow-up on Linux-kernel code accessibility Message-ID: <20251226115136.7107fa1e@gandalf.local.home> In-Reply-To: References: <90d56d30-232d-4930-ad9f-5aebade7cdf2@paulmck-laptop> <636d1798-3b37-293a-51b2-55d2ecc6d2d@inria.fr> <20251219170945.GA32430@macsyma.lan> <20251219132812.2a3516df@gandalf.local.home> <20251222104209.15e98861@gandalf.local.home> <89457d2d-153e-4274-b485-2ace983cec4f@paulmck-laptop> <20251224091158.6ab443cb@gandalf.local.home> X-Mailer: Claws Mail 3.20.0git84 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 16CDF18 X-Stat-Signature: ga8bz55nbntqkn3rh17af4e4h4wfygta X-Rspamd-Server: rspamout05 X-Session-Marker: 726F737465647440676F6F646D69732E6F7267 X-Session-ID: U2FsdGVkX18FJ9eIi/xPiYXZPBp6gvraaUnDdhpkUmY= X-HE-Tag: 1766767898-59685 X-HE-Meta: U2FsdGVkX196aEeD06elesw5cNDV7mx+24VFiQQjIAALYgskqdYHP43d+kAI3KuuQUHoVbw5bCrBugTyjSMkbsi4SJfBjZeIeg7fOqgIRAPVHlgJ/w1wJbVQcx2cQFnstEZM20hyCfx7quBeegkFiyhL3S87xNX+qy6rfZ3OCQbXyhY2Z4L6xkSB7Qx7Y7xB6bkoSrT8ayAS0H0yJqdKyMH6C2tpfzB5CIpiJAQ8gbXHMiFwllzN6QIxM9NN8BL4pdgcT2qVrX5iwt6MRLOq9vaqIV5xUXRHPwDMGvbznCgj3ALyll5fFSdBlVoR2MfCyvyi5vQjEysNFm5kN7l7mAq/0wahDXAg On Thu, 25 Dec 2025 10:18:20 -0800 "Paul E. McKenney" wrote: > > I'm not sure what you mean by "walkthroughs". AI can help give a general > > idea on code, but it still needs the author of the code to verify it. > > So let's kill two birds with one stone. Let's arrange a walkthrough > of this code (starting from its calling function rcu_gp_kthread() some > time after the new year. That will show you how a walkthrough works > (or at least one walkthrough method) and also answer your questions > about the variable "j". Sure, I'll be up for that. > > There's a bit of magical manipulation of "j" that I have no idea why it's > > doing that. ;-) > > Back in the old days, I used to put inline comments on local variables, > but this practice did not spark joy in the Linux kernel community back > in the very early 2000s. Matters how much comments that was I guess. And how useful they were. Today, I believe people want comments. The kernel is much more complex today then it was back in the early 2000s. > > So another question for our walkthrough: Should this practice be > introduced into the Linux kernel? I can't answer that until after the walkthrough ;-) > > > I would love if Julia or Gabriele came up with some specification for that > > function. > > Sounds like a worthy challenge to me! Me, I would open it up to all > comers, but I was clearly willing to give Julia and Gabriele a one-day > head start, even if it was rather inconveniently timed. ;-) I'll let them speak for themselves. -- Steve