From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/14005] New: don't freak on overlong kernel module relocs
Date: Fri, 20 Apr 2012 18:29:00 -0000 [thread overview]
Message-ID: <bug-14005-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14005
Bug #: 14005
Summary: don't freak on overlong kernel module relocs
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: fche@redhat.com
Classification: Unclassified
OK, so a user loads fglrx or some other c++ kernel module. Now they have
relocation sections with long names, including such beauties as
115
.gnu.linkonce.r._ZZN6AsicSII20ucode_class_pitcairnE24programApertureRegistersEjP14APERTURE_STATEE15UPPER_BOUND_GAP
116
.gnu.linkonce.t._ZN6AsicSII20ucode_class_pitcairnE23initializeApertureStateEP14APERTURE_STATEP18SURFACE_PROPERTIESm
136
.gnu.linkonce.t._ZNK25CMMHeap_FRAME_BUFFER_COREI18CMMHeap_ASIC_LOCALE20get_addr_restrictionER16MSF_SURF_ATTRIBSP21MEMHEAP_ADDR_RESTRICT
138
.gnu.linkonce.t._ZN18VMDomainManager_NI17CreateVmDomainsNII14VMDomainNI_PIO14VMDomainNI_PM417VMDomainNI_DRMDMAEEb22_VM_PROGRAMMING_METHOD
138
.gnu.linkonce.t._ZN18VMDomainManager_NI17CreateVmDomainsNII14VMDomainNI_PIO14VMDomainNI_PM417VMDomainSI_DRMDMAEEb22_VM_PROGRAMMING_METHOD
for a glorious maximum "section name" length of 138.
With bug #12612, we've once bumped up the symbol length limits, but not enough.
Nothing is ever enough, when you have enough C++ templates! So we need some
combination of relaxing limits more and/or keeping staprun from giving up so
pessimistically in case of an overlong reloc name.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-04-20 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 18:29 fche at redhat dot com [this message]
2012-04-20 18:39 ` [Bug runtime/14005] " cme3000 at gmail dot com
2012-04-20 18:41 ` fche 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-14005-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).