From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: Rickard Andersson <rickaran@axis.com>, linux-kernel@vger.kernel.org
Cc: rickard314.andersson@gmail.com, mliska@suse.cz
Subject: Re: [PATCH] gcov: Add support for checksum field
Date: Mon, 19 Dec 2022 17:48:14 +0100 [thread overview]
Message-ID: <1da3f764-4445-2135-3292-2912c2e8e778@linux.ibm.com> (raw)
In-Reply-To: <20221219150621.3310033-1-rickaran@axis.com>
On 19.12.2022 16:06, Rickard Andersson wrote:
> From: Rickard x Andersson <rickaran@axis.com>
>
> In GCC version 12.1 a checksum field was added.
Thanks for the patch!
In another e-mail you mentioned that this patch fixes a kernel crash
during boot when using gcov-kernel with GCC 12. Please add this
information to the commit message and if possible the platform on which
this occurs.
Also this patch fixes a missing piece from a previous patch, so please add:
Fixes: 977ef30a7d88 ("gcov: support GCC 12.1 and newer compilers")
Cc: <stable@vger.kernel.org>
Finally I reviewed and tested the patch and it looks good to me, so
please add:
Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
Tested-by: Peter Oberparleiter <oberpar@linux.ibm.com>
Please resend with these commit message changes. Thanks!
For the record: I wondered why my testing of the previous patch with GCC
12 didn't catch this. It turns out that this crash does not occur on
architectures with 8-byte pointer alignment such as s390x where I
performed my tests. Consider this pahole output on s390x without the patch:
struct gcov_info {
[...]
unsigned int stamp; /* 16 4 */
/* XXX 4 bytes hole, try to pack */
const char * filename; /* 24 8 */
[...]
}
And with the patch:
struct gcov_info {
[...]
unsigned int stamp; /* 16 4 */
unsigned int checksum; /* 20 4 */
const char * filename; /* 24 8 */
[...]
}
As can be seen, the offset of the filename and subsequent fields does
not change because the new field fills an alignment hole. It would
change (resulting in a crash during boot) if the alignment-requirement
of the const char *filename field would be different.
>
> Signed-off-by: Rickard x Andersson <rickaran@axis.com>
> ---
> 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;
--
Peter Oberparleiter
Linux on IBM Z Development - IBM Germany R&D
next prev parent reply other threads:[~2022-12-19 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 15:06 [PATCH] gcov: Add support for checksum field Rickard Andersson
2022-12-19 16:48 ` Peter Oberparleiter [this message]
2022-12-20 12:12 ` Martin Liška
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=1da3f764-4445-2135-3292-2912c2e8e778@linux.ibm.com \
--to=oberpar@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mliska@suse.cz \
--cc=rickaran@axis.com \
--cc=rickard314.andersson@gmail.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: 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).