From: Stephen Boyd <swboyd@chromium.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Alexei Starovoitov <ast@kernel.org>, Jessica Yu <jeyu@kernel.org>,
Evan Green <evgreen@chromium.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v3 03/12] dump_stack: Add vmlinux build ID to stack traces
Date: Thu, 08 Apr 2021 14:08:28 -0700 [thread overview]
Message-ID: <161791610893.3790633.1523539584166901628@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <161791154751.3790633.14778133079958701015@swboyd.mtv.corp.google.com>
Quoting Stephen Boyd (2021-04-08 12:52:27)
>
> Can you try this patch for x86? I'll dig up some hardware in the meantime.
>
It works for me backported to this 5.10 kernel running on this x86
device I found. I'll wait for you to confirm and then send the next
round.
CPU: 0 PID: 2719 Comm: bash Not tainted 5.10.27 #1 301c09d6713f73cc8761e0ec7c4a50f354819757
Hardware name: Google Grunt/Grunt, BIOS Google_Grunt.11031.115.0 11/15/2019
RIP: 0010:lkdtm_WARNING+0x13/0x17 [lkdtm bf9f9188770187b40e576292363651839854180c]
Code: c7 15 ae 71 c0 31 c0 e8 b1 f9 f6 c9 0f 1f 44 00 00 55 48 89 e5 0f 0b 0f 1f 44 00 00 55 48 89 e5 ff 05 f3 7d 00 00 75 02 5d c3 <0f> 0b eb fa 0f 1f 44 00 00 55 48 89 e5 8b 35 dc 7d 00 00 ff c6 89
RSP: 0018:ffffb296c1757dc0 EFLAGS: 00010202
RAX: 0000000000000026 RBX: ffffffffc071a060 RCX: 5d63534cda001100
RDX: ffff8e5faac22cf8 RSI: ffff8e5faac12e08 RDI: ffffffffc071a060
RBP: ffffb296c1757dc0 R08: 0000000000000000 R09: ffffb296c1757ba0
R10: 00000000ffffdfff R11: ffffffffc071722e R12: 0000000000000008
R13: ffff8e5fa615f000 R14: ffffffffffffffea R15: ffffffffc071a819
FS: 00007ee3373f2740(0000) GS:ffff8e5faac00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000058d943914918 CR3: 000000000f0a0000 CR4: 00000000001506f0
Call Trace:
direct_entry+0x107/0x113 [lkdtm bf9f9188770187b40e576292363651839854180c]
full_proxy_write+0x5b/0x78
vfs_write+0x145/0x40d
ksys_write+0x7e/0xde
do_syscall_64+0x43/0x55
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7ee3372cb7f4
Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 31 40 0c 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89
RSP: 002b:00007ffe1c6db648 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007ee3372cb7f4
RDX: 0000000000000008 RSI: 000058d944343c60 RDI: 0000000000000001
RBP: 00007ffe1c6db670 R08: 000000000000000a R09: 00007ee3373f2740
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000008
R13: 000058d944343c60 R14: 00007ee33738b5c0 R15: 00007ee3373865c0
next prev parent reply other threads:[~2021-04-08 21:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 3:05 [PATCH v3 00/12] Add build ID to stacktraces Stephen Boyd
2021-03-31 3:05 ` Stephen Boyd
2021-03-31 3:05 ` Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 01/12] buildid: Add API to parse build ID out of buffer Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 02/12] buildid: Stash away kernels build ID on init Stephen Boyd
2021-03-31 3:05 ` Stephen Boyd
2021-04-08 12:05 ` Jessica Yu
2021-04-08 12:05 ` Jessica Yu
2021-04-08 18:52 ` Stephen Boyd
2021-04-08 18:52 ` Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 03/12] dump_stack: Add vmlinux build ID to stack traces Stephen Boyd
2021-04-07 13:42 ` Petr Mladek
2021-04-08 5:44 ` Stephen Boyd
2021-04-07 14:03 ` Petr Mladek
2021-04-08 1:14 ` Stephen Boyd
2021-04-08 6:20 ` Stephen Boyd
2021-04-08 10:13 ` Petr Mladek
2021-04-08 19:52 ` Stephen Boyd
2021-04-08 21:08 ` Stephen Boyd [this message]
2021-04-09 9:19 ` Petr Mladek
2021-03-31 3:05 ` [PATCH v3 04/12] module: Add printk format to add module build ID to stacktraces Stephen Boyd
2021-04-07 14:54 ` Petr Mladek
2021-04-07 15:07 ` Andy Shevchenko
2021-04-07 15:03 ` Petr Mladek
2021-04-07 15:37 ` Andy Shevchenko
2021-04-08 6:58 ` Stephen Boyd
2021-04-08 13:44 ` Jessica Yu
2021-04-08 14:05 ` Andy Shevchenko
2021-04-08 19:57 ` Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 05/12] arm64: stacktrace: Use %pSb for backtrace printing Stephen Boyd
2021-03-31 3:05 ` Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 06/12] x86/dumpstack: " Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 07/12] scripts/decode_stacktrace.sh: Support debuginfod Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 08/12] scripts/decode_stacktrace.sh: Silence stderr messages from addr2line/nm Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 09/12] scripts/decode_stacktrace.sh: Indicate 'auto' can be used for base path Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 10/12] buildid: Mark some arguments const Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 11/12] buildid: Fix kernel-doc notation Stephen Boyd
2021-03-31 3:05 ` [PATCH v3 12/12] kdump: Use vmlinux_build_id to simplify Stephen Boyd
2021-03-31 3:05 ` Stephen Boyd
2021-04-07 17:03 ` Petr Mladek
2021-04-07 17:03 ` Petr Mladek
2021-04-08 5:36 ` Stephen Boyd
2021-04-08 5:36 ` Stephen Boyd
2021-04-08 10:17 ` Baoquan He
2021-04-08 10:17 ` Baoquan He
2021-04-08 19:58 ` Stephen Boyd
2021-04-08 19:58 ` Stephen Boyd
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=161791610893.3790633.1523539584166901628@swboyd.mtv.corp.google.com \
--to=swboyd@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ast@kernel.org \
--cc=evgreen@chromium.org \
--cc=hsinyi@chromium.org \
--cc=jeyu@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.