From: Rickard Andersson <rickaran@axis.com>
To: <linux-kernel@vger.kernel.org>, <oberpar@linux.ibm.com>
Cc: <rickard314.andersson@gmail.com>, <mliska@suse.cz>,
<Jesper.Nilsson@axis.com>,
Rickard x Andersson <rickaran@axis.com>, <stable@vger.kernel.org>
Subject: [PATCH v2] gcov: Add support for checksum field
Date: Tue, 20 Dec 2022 11:23:18 +0100 [thread overview]
Message-ID: <20221220102318.3418501-1-rickaran@axis.com> (raw)
From: Rickard x Andersson <rickaran@axis.com>
In GCC version 12.1 a checksum field was added.
This patch fixes a kernel crash occurring during boot when
using gcov-kernel with GCC version 12.2. The crash occurred on
a system running on i.MX6SX.
Fixes: 977ef30a7d88 ("gcov: support GCC 12.1 and newer compilers")
Signed-off-by: Rickard x Andersson <rickaran@axis.com>
Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
Tested-by: Peter Oberparleiter <oberpar@linux.ibm.com>
Cc: <stable@vger.kernel.org>
---
kernel/gcov/gcc_4_7.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/kernel/gcov/gcc_4_7.c b/kernel/gcov/gcc_4_7.c
index c699feda21ac..04880d8fba25 100644
--- a/kernel/gcov/gcc_4_7.c
+++ b/kernel/gcov/gcc_4_7.c
@@ -85,6 +85,7 @@ struct gcov_fn_info {
* @version: gcov version magic indicating the gcc version used for compilation
* @next: list head for a singly-linked list
* @stamp: uniquifying time stamp
+ * @checksum: unique object checksum
* @filename: name of the associated gcov data file
* @merge: merge functions (null for unused counter type)
* @n_functions: number of instrumented functions
@@ -97,6 +98,10 @@ struct gcov_info {
unsigned int version;
struct gcov_info *next;
unsigned int stamp;
+ /* Since GCC 12.1 a checksum field is added. */
+#if (__GNUC__ >= 12)
+ unsigned int checksum;
+#endif
const char *filename;
void (*merge[GCOV_COUNTERS])(gcov_type *, unsigned int);
unsigned int n_functions;
--
2.30.2
next reply other threads:[~2022-12-20 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 10:23 Rickard Andersson [this message]
2022-12-20 17:53 ` Peter Oberparleiter
2022-12-20 17:57 ` Peter Oberparleiter
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=20221220102318.3418501-1-rickaran@axis.com \
--to=rickaran@axis.com \
--cc=Jesper.Nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mliska@suse.cz \
--cc=oberpar@linux.ibm.com \
--cc=rickard314.andersson@gmail.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®