Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1697164ybg; Thu, 4 Jun 2020 17:04:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzaCEyr4nMU/7mZyIaqM3XNflwpvaQbYfgicEOffEFtIaF5Uxi3NEbsdVCKqoVOgd0mUyW2 X-Received: by 2002:a50:e444:: with SMTP id e4mr6432109edm.191.1591315497778; Thu, 04 Jun 2020 17:04:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591315497; cv=none; d=google.com; s=arc-20160816; b=ThX+fLV0Cheeb1hqm6FvF/1FT8SobKIJrhut6UyAeTwiRlncLvZ6CWVVeMp6mYEgUt Ba0+BnS7sYZYLBAAzyhDAmSHW6I7D4o0zSNW4EMBMvfu+VDj9cWmTemCiWWx/pNXHfcd UErUI55seoSrVpnWVPr3kkRtqPWwpbJZM47o81O/clWOm3iQNDgDU5vG+pJMDEOfiAmf fEm58x9GKpgH8y6O4E+2tho6CLB3mltM2Mgi9EDRvmBtoaZ83yYHrz9lwHHIIQ1QGu9o /4fgfIFNpgoHng5Qb5OJgF1wlloKmGcF48gQctFOKZ2t0wSrvlwKn3yaSey0ym7Hf6Fc x9+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature:dkim-filter; bh=9JL8mvQwy+Q0hLJa7h0p6p7R2yQdcRE5qvZum3vex+Y=; b=fzLFRAX+Qx6LQrfqnC8BWQaKpktpA95Ou9r37taKFq0CgYa5KJKPDFisVHPyUA1/ka /C3zCByAkD1rOkMyiTpsNMXJvcYkE0965cfPHpX/Fd4MwuJPxKrmMALz1yIUewU0q09O vLeysmr2nI0/+7mkO9dDZk7oQdbfNJtoKq7sAK9Uf9rbmV+N13o4DTsMb+KijfD5gnAI JAj7ibhNUVv7GDkcbuy1T0cSzcJDLa4F0PW04frLhN5/tZOTTwJu3Cc0IgolHgfdH1pd zcPU3m1mbV+V0tqQvCLplgOdKcIPcxjwpqWBHv/2W0A40h7q2hS8K7QlrT0pB5+uaHCC aG4A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=fsyQpS9Y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bk19si2377835ejb.669.2020.06.04.17.04.18; Thu, 04 Jun 2020 17:04:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=fsyQpS9Y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726026AbgFEABi (ORCPT + 99 others); Thu, 4 Jun 2020 20:01:38 -0400 Received: from linux.microsoft.com ([13.77.154.182]:40412 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725955AbgFEABi (ORCPT ); Thu, 4 Jun 2020 20:01:38 -0400 Received: from linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net (linux.microsoft.com [13.77.154.182]) by linux.microsoft.com (Postfix) with ESMTPSA id 1825120B7185; Thu, 4 Jun 2020 17:01:37 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 1825120B7185 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1591315297; bh=9JL8mvQwy+Q0hLJa7h0p6p7R2yQdcRE5qvZum3vex+Y=; h=From:To:Cc:Subject:Date:From; b=fsyQpS9Ye//xpHqVE9xVfUsQHlvFw8Q30QqvOwrES88tCaNh4XNagB19t1AQK+WtZ dfi8SVmu2FpDC4BoraVAuLfCWRaWEDYiT6sX9jHgu/JzuBA4Q8FxL52eL9sbMzBsE5 YDUUlnclvbzpTQW3PvTeApIZ8xnZY2DC442ee4zQ= From: Vijay Balakrishna To: Dave Young , Baoquan He Cc: Vivek Goyal , kexec@lists.infradead.org, linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com, Tyler Hicks Subject: [PATCH][RFC] kdump: append kernel build-id string to VMCOREINFO Date: Thu, 4 Jun 2020 17:01:31 -0700 Message-Id: <1591315291-66957-1-git-send-email-vijayb@linux.microsoft.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Make kernel GNU build-id available in VMCOREINFO. Having build-id in VMCOREINFO facilitates presenting appropriate kernel namelist image with debug information file to kernel crash dump analysis tools. Currently VMCOREINFO lacks uniquely identifiable key for crash analysis automation. Signed-off-by: Vijay Balakrishna --- Regarding if this patch is necessary or matching of linux_banner and OSRELEASE in VMCOREINFO employed by crash(8) meets the need -- IMO, build-id approach more foolproof, in most instances it is a cryptographic hash generated using internal code/ELF bits unlike kernel version string upon which linux_banner is based that is external to the code. I feel each is intended for a different purpose. Also OSRELEASE is not suitable when two different kernel builds from same version with different features enabled. Currently for most linux (and non-linux) systems build-id can be extracted using standard methods for file types such as user mode crash dumps, shared libraries, loadable kernel modules etc. This is an exception for linux kernel dump. Having build-id in VMCOREINFO brings some uniformity for automation tools. include/linux/crash_core.h | 6 +++++ kernel/crash_core.c | 50 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/include/linux/crash_core.h b/include/linux/crash_core.h index 525510a9f965..6594dbc34a37 100644 --- a/include/linux/crash_core.h +++ b/include/linux/crash_core.h @@ -38,6 +38,8 @@ phys_addr_t paddr_vmcoreinfo_note(void); #define VMCOREINFO_OSRELEASE(value) \ vmcoreinfo_append_str("OSRELEASE=%s\n", value) +#define VMCOREINFO_BUILD_ID(value) \ + vmcoreinfo_append_str("BUILD-ID=%s\n", value) #define VMCOREINFO_PAGESIZE(value) \ vmcoreinfo_append_str("PAGESIZE=%ld\n", value) #define VMCOREINFO_SYMBOL(name) \ @@ -64,6 +66,10 @@ extern unsigned char *vmcoreinfo_data; extern size_t vmcoreinfo_size; extern u32 *vmcoreinfo_note; +/* raw contents of kernel .notes section */ +extern const void __start_notes __weak; +extern const void __stop_notes __weak; + Elf_Word *append_elf_note(Elf_Word *buf, char *name, unsigned int type, void *data, size_t data_len); void final_note(Elf_Word *buf); diff --git a/kernel/crash_core.c b/kernel/crash_core.c index 9f1557b98468..c094db478803 100644 --- a/kernel/crash_core.c +++ b/kernel/crash_core.c @@ -11,6 +11,8 @@ #include #include +#include + /* vmcoreinfo stuff */ unsigned char *vmcoreinfo_data; size_t vmcoreinfo_size; @@ -376,6 +378,53 @@ phys_addr_t __weak paddr_vmcoreinfo_note(void) } EXPORT_SYMBOL(paddr_vmcoreinfo_note); +#define NOTES_SIZE (&__stop_notes - &__start_notes) +#define BUILD_ID_MAX SHA1_DIGEST_SIZE +#define NT_GNU_BUILD_ID 3 + +struct elf_note_section { + struct elf_note n_hdr; + u8 n_data[]; +}; + +/* + * Add build ID from .notes section as generated by the GNU ld(1) + * or LLVM lld(1) --build-id option. + */ +static void add_build_id_vmcoreinfo(void) +{ + char build_id[BUILD_ID_MAX * 2 + 1]; + int n_remain = NOTES_SIZE; + + while (n_remain >= sizeof(struct elf_note)) { + const struct elf_note_section *g_build_id = + &__start_notes + NOTES_SIZE - n_remain; + const u32 n_namesz = g_build_id->n_hdr.n_namesz; + + if (g_build_id->n_hdr.n_type == NT_GNU_BUILD_ID && + n_namesz != 0 && + !strcmp((char *)&g_build_id->n_data[0], "GNU")) { + if (g_build_id->n_hdr.n_descsz <= BUILD_ID_MAX) { + const u32 n_descsz = g_build_id->n_hdr.n_descsz; + const u8 *s = &g_build_id->n_data[n_namesz]; + + s = PTR_ALIGN(s, 4); + bin2hex(build_id, s, n_descsz); + build_id[2 * n_descsz] = '\0'; + VMCOREINFO_BUILD_ID(build_id); + return; + } + pr_warn("Build ID is too large to include in vmcoreinfo: %lu > %lu\n", + g_build_id->n_hdr.n_descsz, + BUILD_ID_MAX); + return; + } + n_remain -= sizeof(struct elf_note) + + ALIGN(g_build_id->n_hdr.n_namesz, 4) + + ALIGN(g_build_id->n_hdr.n_descsz, 4); + } +} + static int __init crash_save_vmcoreinfo_init(void) { vmcoreinfo_data = (unsigned char *)get_zeroed_page(GFP_KERNEL); @@ -394,6 +443,7 @@ static int __init crash_save_vmcoreinfo_init(void) } VMCOREINFO_OSRELEASE(init_uts_ns.name.release); + add_build_id_vmcoreinfo(); VMCOREINFO_PAGESIZE(PAGE_SIZE); VMCOREINFO_SYMBOL(init_uts_ns); -- 2.26.2