From: Boqun Feng <boqun.feng@gmail.com>
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
Date: Wed, 7 Aug 2024 20:39:25 -0700 [thread overview]
Message-ID: <ZrQ97Zz27Tzmr0Zi@tardis> (raw)
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(-)
next reply other threads:[~2024-08-08 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 3:39 Boqun Feng [this message]
2024-08-08 10:19 ` Peter Zijlstra
2024-08-08 16:11 ` Boqun Feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZrQ97Zz27Tzmr0Zi@tardis \
--to=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=neeraj.iitr10@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®