From: Ingo Molnar <mingo@kernel.org>
To: Byungchul Park <byungchul.park@lge.com>
Cc: peterz@infradead.org, axboe@kernel.dk, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, tj@kernel.org,
johannes.berg@intel.com, oleg@redhat.com, amir73il@gmail.com,
david@fromorbit.com, darrick.wong@oracle.com,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org, hch@infradead.org,
idryomov@gmail.com, kernel-team@lge.com
Subject: Re: [PATCH v3 4/8] lockdep: Add a kernel parameter, crossrelease_fullstack
Date: Tue, 24 Oct 2017 12:08:58 +0200 [thread overview]
Message-ID: <20171024100858.2rw7wnhtj7d3iyzk@gmail.com> (raw)
In-Reply-To: <1508837889-16932-5-git-send-email-byungchul.park@lge.com>
* Byungchul Park <byungchul.park@lge.com> wrote:
> Make whether to allow recording full stack, in cross-release feature,
> switchable at boot time via a kernel parameter, 'crossrelease_fullstack'.
> In case of a splat with no stack trace, one could just reboot and set
> the kernel parameter to get the full data without having to recompile
> the kernel.
>
> Change CONFIG_CROSSRELEASE_STACK_TRACE default from N to Y, and
> introduce the new kernel parameter.
>
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 3 +++
> kernel/locking/lockdep.c | 18 ++++++++++++++++--
> lib/Kconfig.debug | 5 +++--
> 3 files changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index ead7f40..4107b01 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -709,6 +709,9 @@
> It will be ignored when crashkernel=X,high is not used
> or memory reserved is below 4G.
>
> + crossrelease_fullstack
> + [KNL] Allow to record full stack trace in cross-release
> +
> cryptomgr.notests
> [KNL] Disable crypto self-tests
>
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index 5c2ddf2..feba887 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -76,6 +76,15 @@
> #define lock_stat 0
> #endif
>
> +static int crossrelease_fullstack;
> +static int __init allow_crossrelease_fullstack(char *str)
> +{
> + crossrelease_fullstack = 1;
> + return 0;
> +}
> +
> +early_param("crossrelease_fullstack", allow_crossrelease_fullstack);
> +
> /*
> * lockdep_lock: protects the lockdep graph, the hashes and the
> * class/list/hash allocators.
> @@ -4864,8 +4873,13 @@ static void add_xhlock(struct held_lock *hlock)
> xhlock->trace.max_entries = MAX_XHLOCK_TRACE_ENTRIES;
> xhlock->trace.entries = xhlock->trace_entries;
> #ifdef CONFIG_CROSSRELEASE_STACK_TRACE
> - xhlock->trace.skip = 3;
> - save_stack_trace(&xhlock->trace);
> + if (crossrelease_fullstack) {
> + xhlock->trace.skip = 3;
> + save_stack_trace(&xhlock->trace);
> + } else {
> + xhlock->trace.nr_entries = 1;
> + xhlock->trace.entries[0] = hlock->acquire_ip;
> + }
> #else
> xhlock->trace.nr_entries = 1;
> xhlock->trace.entries[0] = hlock->acquire_ip;
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index fe8fceb..132536d 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1228,7 +1228,7 @@ config LOCKDEP_COMPLETIONS
> config CROSSRELEASE_STACK_TRACE
> bool "Record more than one entity of stack trace in crossrelease"
> depends on LOCKDEP_CROSSRELEASE
> - default n
> + default y
> help
> The lockdep "cross-release" feature needs to record stack traces
> (of calling functions) for all acquisitions, for eventual later
> @@ -1238,7 +1238,8 @@ config CROSSRELEASE_STACK_TRACE
> full analysis. This option turns on the saving of the full stack
> trace entries.
>
> - If unsure, say N.
> + To make the feature actually on, set "crossrelease_fullstack"
> + kernel parameter, too.
>
> config DEBUG_LOCKDEP
> bool "Lock dependency engine debugging"
This is really unnecessarily complex.
The proper logic is to introduce the crossrelease_fullstack boot parameter, and to
also have a Kconfig option that enables it:
CONFIG_BOOTPARAM_LOCKDEP_CROSSRELEASE_FULLSTACK=y
No #ifdefs please - just an "if ()" branch dependent on the current value of
crossrelease_fullstack.
Thanks,
Ingo
next prev parent reply other threads:[~2017-10-24 10:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 9:38 [PATCH v3 0/8] cross-release: enhence performance and fix false positives Byungchul Park
2017-10-24 9:38 ` [PATCH v3 1/8] block: use DECLARE_COMPLETION_ONSTACK in submit_bio_wait Byungchul Park
2017-10-24 9:38 ` [PATCH v3 2/8] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default Byungchul Park
2017-10-24 10:05 ` Ingo Molnar
2017-10-25 1:01 ` Byungchul Park
2017-10-25 5:53 ` Ingo Molnar
2017-10-24 10:06 ` Ingo Molnar
2017-10-24 9:38 ` [PATCH v3 3/8] lockdep: Remove BROKEN flag of LOCKDEP_CROSSRELEASE Byungchul Park
2017-10-24 10:06 ` Ingo Molnar
2017-10-24 9:38 ` [PATCH v3 4/8] lockdep: Add a kernel parameter, crossrelease_fullstack Byungchul Park
2017-10-24 10:08 ` Ingo Molnar [this message]
2017-10-24 23:45 ` Byungchul Park
2017-10-24 9:38 ` [PATCH v3 5/8] completion: Add support for initializing completion with lockdep_map Byungchul Park
2017-10-24 9:38 ` [PATCH v3 6/8] lockdep: Remove unnecessary acquisitions wrt workqueue flush Byungchul Park
2017-10-24 9:38 ` [PATCH v3 7/8] genhd.h: Remove trailing white space Byungchul Park
2017-10-24 10:10 ` Ingo Molnar
2017-10-24 9:38 ` [PATCH v3 8/8] block: Assign a lock_class per gendisk used for wait_for_completion() Byungchul Park
2017-10-24 10:15 ` Ingo Molnar
2017-10-25 0:26 ` Byungchul Park
2017-10-25 5:55 ` Ingo Molnar
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=20171024100858.2rw7wnhtj7d3iyzk@gmail.com \
--to=mingo@kernel.org \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=byungchul.park@lge.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=idryomov@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kernel-team@lge.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).