From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30459] New: Ko compilation failures with kernel 6.1/6.2 kernel headers
Date: Thu, 18 May 2023 05:33:12 +0000 [thread overview]
Message-ID: <bug-30459-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30459
Bug ID: 30459
Summary: Ko compilation failures with kernel 6.1/6.2 kernel
headers
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
For some nontrivial stap scripts compiled with Fedora 36's 6.1 and 6.2 kernels,
the kernel build system trows out the following compilation errors:
```
In file included from
/opt/stap-plus/share/systemtap/runtime/linux/runtime.h:301,
from /opt/stap-plus/share/systemtap/runtime/runtime.h:26,
from
/tmp/stapzRqxL5/stap_61c4c192c40cf6ad899afb44bb419d45_1848_src.c:17:
/opt/stap-plus/share/systemtap/runtime/sym.c: In function
‘_stp_usermodule_check’:
/opt/stap-plus/share/systemtap/runtime/sym.c:983:1: error: the frame size of
2056 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
983 | }
| ^
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:250:
/tmp/stapzRqxL5/stap_61c4c192c40cf6ad899afb44bb419d45_1848_src.o] Error 1
make: *** [Makefile:2016: /tmp/stapzRqxL5] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
```
An unused C array is allocated on the stack, which triggers this error. I'll
prepare a patch to fix this.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-05-18 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 5:33 agentzh at gmail dot com [this message]
2023-05-18 5:46 ` [Bug runtime/30459] " agentzh at gmail dot com
2023-05-25 19:10 ` wcohen at redhat dot com
2023-06-07 17:57 ` wcohen at redhat dot com
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=bug-30459-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).