From: Jessica Yu <jeyu@kernel.org> To: Stephen Boyd <swboyd@chromium.org> Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>, Evan Green <evgreen@chromium.org>, Hsin-Yi Wang <hsinyi@chromium.org>, Dave Young <dyoung@redhat.com>, Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>, kexec@lists.infradead.org Subject: Re: [PATCH v3 02/12] buildid: Stash away kernels build ID on init Date: Thu, 8 Apr 2021 14:05:33 +0200 [thread overview] Message-ID: <YG7xjbIEmrCco14F@gunter> (raw) In-Reply-To: <20210331030520.3816265-3-swboyd@chromium.org> +++ Stephen Boyd [30/03/21 20:05 -0700]: [snipped] >diff --git a/lib/buildid.c b/lib/buildid.c >index 010ab0674cb9..b939bbc59233 100644 >--- a/lib/buildid.c >+++ b/lib/buildid.c >@@ -1,6 +1,7 @@ > // SPDX-License-Identifier: GPL-2.0 > > #include <linux/buildid.h> >+#include <linux/cache.h> > #include <linux/elf.h> > #include <linux/kernel.h> > #include <linux/pagemap.h> >@@ -171,3 +172,19 @@ int build_id_parse_buf(const void *buf, unsigned char *build_id, u32 buf_size) > { > return parse_build_id_buf(build_id, NULL, buf, buf_size); > } >+ >+unsigned char vmlinux_build_id[BUILD_ID_SIZE_MAX] __ro_after_init; >+ >+/** >+ * init_vmlinux_build_id - Get the running kernel's build ID >+ * >+ * Return: Running kernel's build ID >+ */ Hm, init_vmlinux_build_id() doesn't return anything, so this comment is not accurate - maybe "Get the running kernel's build ID and store it in vmlinux_build_id"? >+void __init init_vmlinux_build_id(void) >+{ >+ extern const void __start_notes __weak; >+ extern const void __stop_notes __weak; >+ unsigned int size = &__stop_notes - &__start_notes; >+ >+ build_id_parse_buf(&__start_notes, vmlinux_build_id, size); >+}
WARNING: multiple messages have this Message-ID (diff)
From: Jessica Yu <jeyu@kernel.org> To: Stephen Boyd <swboyd@chromium.org> Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>, Evan Green <evgreen@chromium.org>, Hsin-Yi Wang <hsinyi@chromium.org>, Dave Young <dyoung@redhat.com>, Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>, kexec@lists.infradead.org Subject: Re: [PATCH v3 02/12] buildid: Stash away kernels build ID on init Date: Thu, 8 Apr 2021 14:05:33 +0200 [thread overview] Message-ID: <YG7xjbIEmrCco14F@gunter> (raw) In-Reply-To: <20210331030520.3816265-3-swboyd@chromium.org> +++ Stephen Boyd [30/03/21 20:05 -0700]: [snipped] >diff --git a/lib/buildid.c b/lib/buildid.c >index 010ab0674cb9..b939bbc59233 100644 >--- a/lib/buildid.c >+++ b/lib/buildid.c >@@ -1,6 +1,7 @@ > // SPDX-License-Identifier: GPL-2.0 > > #include <linux/buildid.h> >+#include <linux/cache.h> > #include <linux/elf.h> > #include <linux/kernel.h> > #include <linux/pagemap.h> >@@ -171,3 +172,19 @@ int build_id_parse_buf(const void *buf, unsigned char *build_id, u32 buf_size) > { > return parse_build_id_buf(build_id, NULL, buf, buf_size); > } >+ >+unsigned char vmlinux_build_id[BUILD_ID_SIZE_MAX] __ro_after_init; >+ >+/** >+ * init_vmlinux_build_id - Get the running kernel's build ID >+ * >+ * Return: Running kernel's build ID >+ */ Hm, init_vmlinux_build_id() doesn't return anything, so this comment is not accurate - maybe "Get the running kernel's build ID and store it in vmlinux_build_id"? >+void __init init_vmlinux_build_id(void) >+{ >+ extern const void __start_notes __weak; >+ extern const void __stop_notes __weak; >+ unsigned int size = &__stop_notes - &__start_notes; >+ >+ build_id_parse_buf(&__start_notes, vmlinux_build_id, size); >+} _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2021-04-08 12:05 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 [this message] 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 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=YG7xjbIEmrCco14F@gunter \ --to=jeyu@kernel.org \ --cc=akpm@linux-foundation.org \ --cc=ast@kernel.org \ --cc=bhe@redhat.com \ --cc=dyoung@redhat.com \ --cc=evgreen@chromium.org \ --cc=hsinyi@chromium.org \ --cc=jolsa@kernel.org \ --cc=kexec@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=swboyd@chromium.org \ --cc=vgoyal@redhat.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: linkBe 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.