linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: mingo@kernel.org, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	jolsa@redhat.com, alexey.budankov@linux.intel.com,
	songliubraving@fb.com, acme@redhat.com, allison@lohutok.net,
	Sasha Levin <sashal@kernel.org>
Subject: [PATCH v2 10/12] tools/lib/lockdep: New stacktrace API
Date: Sat, 18 Apr 2020 21:57:52 -0400	[thread overview]
Message-ID: <20200419015754.24456-11-sashal@kernel.org> (raw)
In-Reply-To: <20200419015754.24456-1-sashal@kernel.org>

The kernel switched to using kernel/stacktrace.c, and the API slightly
changed.

Adjust it to make stack traces work again.

Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 tools/include/linux/stacktrace.h | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/tools/include/linux/stacktrace.h b/tools/include/linux/stacktrace.h
index ae343ac35bfa7..b290b98d883aa 100644
--- a/tools/include/linux/stacktrace.h
+++ b/tools/include/linux/stacktrace.h
@@ -15,10 +15,18 @@ static inline void print_stack_trace(struct stack_trace *trace, int spaces)
 	backtrace_symbols_fd((void **)trace->entries, trace->nr_entries, 1);
 }
 
+static inline void stack_trace_print(const long unsigned int *entries, unsigned int nr, int spaces)
+{
+	backtrace_symbols_fd((void **)entries, nr, 1);
+}
+
 #define save_stack_trace(trace)	\
 	((trace)->nr_entries =	\
 		backtrace((void **)(trace)->entries, (trace)->max_entries))
 
+#define stack_trace_save(e, m, x) \
+	backtrace((void **)(e), (m))
+
 static inline int dump_stack(void)
 {
 	void *array[64];
-- 
2.20.1


  parent reply	other threads:[~2020-04-19  1:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  1:57 [PATCH v2 00/12] Fix up liblockdep for 5.7-rc Sasha Levin
2020-04-19  1:57 ` [PATCH v2 01/12] tools headers: Add kprobes.h header Sasha Levin
2020-04-19  1:57 ` [PATCH v2 02/12] tools headers: Add rcupdate.h header Sasha Levin
2020-04-19  1:57 ` [PATCH v2 03/12] tools/kernel.h: extend with dummy RCU functions Sasha Levin
2020-04-19  1:57 ` [PATCH v2 04/12] tools bitmap: add bitmap_andnot definition Sasha Levin
2020-04-19  1:57 ` [PATCH v2 05/12] tools/lib/lockdep: add definition required for IRQ flag tracing Sasha Levin
2020-04-19  1:57 ` [PATCH v2 06/12] tools/kernel.h: add BUILD_BUG_ON_NOT_POWER_OF_2 macro Sasha Levin
2020-04-19  1:57 ` [PATCH v2 07/12] tools bitmap: add bitmap_clear definition Sasha Levin
2020-04-19  1:57 ` [PATCH v2 08/12] tools/lib/lockdep: Hook up vsprintf, find_bit, hweight libraries Sasha Levin
2020-04-19  1:57 ` [PATCH v2 09/12] tools/lib/lockdep: Enable building with CONFIG_TRACE_IRQFLAGS Sasha Levin
2020-04-19  1:57 ` Sasha Levin [this message]
2020-04-19  1:57 ` [PATCH v2 11/12] tools/lib/lockdep: call lockdep_init_task on init Sasha Levin
2020-04-19  1:57 ` [PATCH v2 12/12] tools/lib/lockdep: switch to using lockdep_init_map_waits Sasha Levin
2020-06-01 20:52 ` [PATCH v2 00/12] Fix up liblockdep for 5.7-rc Sasha Levin

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=20200419015754.24456-11-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=allison@lohutok.net \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=songliubraving@fb.com \
    --cc=tglx@linutronix.de \
    /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).