From: Waiman Long <longman@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org,
Yang Shi <yang.shi@linux.alibaba.com>,
Arnd Bergmann <arnd@arndb.de>,
chuhu@redhat.com, Waiman Long <longman@redhat.com>
Subject: [PATCH v2 0/2] debugobjects: Fix potential hard lockup by disabling lockdep
Date: Tue, 25 Sep 2018 10:41:07 -0400 [thread overview]
Message-ID: <1537886469-18227-1-git-send-email-longman@redhat.com> (raw)
v2:
- Add a lockdep patch to fix a dmesg warning message due to the use
of the novalidate class.
The only locking used by the debugobjects code is just 2 sets of raw
spinlocks for synchronization purpose. When lockdep is enabled, the
locking operation itself will become much more expensive especially
if a number of locks have already been acquired previously. In some
extreme cases, it may lead to hard lockup.
As there isn't much value in debugging the debugobjects internal locks,
lockdep checking is now disabled for those internal locks. That will
speed up system operation without compromising the lock checking
operation of production code.
Waiman Long (2):
locking/lockdep: Don't warn class/lock name mismatch for novalidate
class
debugobjects: Disable lockdep tracking of debugobjects internal locks
kernel/locking/lockdep.c | 7 +++++--
lib/debugobjects.c | 9 ++++++++-
2 files changed, 13 insertions(+), 3 deletions(-)
--
2.18.0
next reply other threads:[~2018-09-25 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 14:41 Waiman Long [this message]
2018-09-25 14:41 ` [PATCH v2 1/2] locking/lockdep: Don't warn class/lock name mismatch for novalidate class Waiman Long
2018-09-25 14:41 ` [PATCH v2 2/2] debugobjects: Disable lockdep tracking of debugobjects internal locks Waiman Long
2018-09-25 15:32 ` Peter Zijlstra
2018-09-25 16:20 ` Waiman Long
2018-09-25 16:31 ` Peter Zijlstra
2018-09-25 16:36 ` Waiman Long
2018-09-28 18:33 ` Waiman Long
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=1537886469-18227-1-git-send-email-longman@redhat.com \
--to=longman@redhat.com \
--cc=arnd@arndb.de \
--cc=chuhu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=yang.shi@linux.alibaba.com \
/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®