Date: Wed, 7 Aug 2024 20:39:25 -0700 From: Boqun Feng To: peterz@infradead.org, mingo@redhat.com Cc: will@kernel.org, longman@redhat.com, boqun.feng@gmail.com, linux-kernel@vger.kernel.org, tglx@linutronix.de, paulmck@kernel.org, frederic@kernel.org, josh@joshtriplett.org, neeraj.iitr10@gmail.com, urezki@gmail.com, rcu@vger.kernel.org Subject: [GIT PULL] LOCKDEP changes for v6.12 Hi Peter & Ingo, Per discussion: https://lore.kernel.org/lkml/20240802151619.GN39708@noisy.programming.kicks-ass.net/ I'm sending a PR with some lockdep changes to tip. The following changes since commit d5934e76316e84eced836b6b2bafae1837d1cd58: cleanup: Add usage and style documentation (2024-08-05 16:54:41 +0200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux tags/lockdep-for-tip.20240806 for you to fetch changes up to 39dea484e2bb9066abbc01e2c5e03b6917b0b775: locking/lockdep: Simplify character output in seq_line() (2024-08-06 10:46:43 -0700) I've reviewed and tested these changes from my end, but since I don't have a branch tracked by linux-next, so that part of testing is missing. It does pass the 0day build test though. RCU is Cced since I believe patch: lockdep: fix deadlock issue between lockdep and rcu is also queued in the upcoming RCU PR for v6.12. However, since it's a bug fix in lockdep, I feel it makes more sense to go via tip. Worst case, git merge will eventually find the duplicate commit, so not a problem. I'm doing this "sub-maintenance" via a PR, but I'm also OK to send them as patch series, whatever makes your life easier. ;-) Also since this is a sub-maintenance, I plan to stop pusing anything new after -rc2 for a particular release (i.e. anything new after -rc3 will be in a PR from me in the later release), mostly due to lockdep shouldn't have anything urgent (famous last words though), and give you guys more time to prepare the PRs from the tip tree, but again I'm open to any suggestion as well. ---------------------------------------------------------------- Lockdep changes for v6.12: - Fixes a deadlock in lockdep by avoiding calling rcu with the graph lock held. - Uses str_plural() to fix Coccinelle warning. - Uses seq_putc() instead of seq_printf() to print a single character in lockdep proc file. Regards, Boqun ---------------------------------------------------------------- Markus Elfring (1): locking/lockdep: Simplify character output in seq_line() Thorsten Blum (1): lockdep: Use str_plural() to fix Coccinelle warning Zhiguo Niu (1): lockdep: fix deadlock issue between lockdep and rcu kernel/locking/lockdep.c | 50 ++++++++++++++++++++++++++++--------------- kernel/locking/lockdep_proc.c | 2 +- 2 files changed, 34 insertions(+), 18 deletions(-) . Date: Wed, 14 Aug 2024 09:32:12 -0700 From: "Paul E. McKenney" To: torvalds@linux-foundation.org Cc: neeraj.iitr10@gmail.com, frederic@kernel.org, rcu@vger.kernel.org Subject: Neeraj Upadhyay will do v6.12 RCU pull request, Frederic Weisbecker v6.13 Hello, Linus, Just to let you know that Neeraj Upadhyay will be sending you the RCU pull request for the v6.12 merge window. This is his second time, but the difference is that this time he is also "curating" RCU patches, that is, pulling them in from the mailing lists, doing initial testing, and working out which go into the v6.12 RCU pull request. Frederic Weisbecker will be doing this for the v6.13 merge window. Please let us know if you have any questions or concerns. Thanx, Paul .