Bug 1442561 - unwind failures with 4.10.x fedora kernels
Summary: unwind failures with 4.10.x fedora kernels
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemtap
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Frank Ch. Eigler
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-15 14:02 UTC by Frank Ch. Eigler
Modified: 2017-12-12 10:17 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:17:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2017-04-15 14:02:38 UTC
kernel backtraces have become truncated.

[root@easy cache]# uname -r
4.10.9-200.fc25.x86_64
[root@easy cache]# rpm -q kernel-debuginfo
kernel-debuginfo-4.10.9-200.fc25.x86_64
[root@easy cache]# rpm -q systemtap
systemtap-3.1-2.fc25.x86_64

# stap -e 'probe kernel.function("avc_has_perm"){print_backtrace()exit()}' -d kernel

 0xffffffffa9383940 : avc_has_perm+0x0/0x1a0 [kernel]
 0x0 (inexact)

# stap -e 'probe kernel.function("avc_has_perm"){print_backtrace()exit()}' -DDEBUG_UNWIND -d kernel
_stp_stack_unwind_one_kernel:274: STARTING kernel unwind
 0xffffffffa9383940 : avc_has_perm+0x0/0x1a0 [kernel]
_stp_stack_unwind_one_kernel:309: CONTINUING kernel unwind to depth 1
unwind:1478: pc=ffffffffa9383940, ffffffffa9383940
unwind:1521: trying debug_frame
set_no_state_rule:249: reg=10, where=1
_stp_search_unwind_hdr:775: binary search for ffffffffa9383940
_stp_search_unwind_hdr:840: fde off=1ffea0
_stp_search_unwind_hdr:850: returning fde=ffffffffc1018b80 startLoc=ffffffff821aca76
unwind_frame:1194: /usr/lib/debug/usr/lib/modules/4.10.9-200.fc25.x86_64/vmlinux: fde=ffffffffc1018b80
unwind_frame:1199: /usr/lib/debug/usr/lib/modules/4.10.9-200.fc25.x86_64/vmlinux: cie=ffffffffc1018a98
parse_fde_cie:156: map retAddrReg value 16 to reg_info idx 16
unwind_frame:1214: startLoc: ffffffff821aca76, endLoc: ffffffff821acaaa
unwind_frame:1216: pc (ffffffffa9383940) > endLoc(ffffffff821acaaa)
unwind:1525: debug_frame failed: 1, trying eh_frame
unwind_frame:1178: Module /usr/lib/debug/usr/lib/modules/4.10.9-200.fc25.x86_64/vmlinux: no unwind frame data
_stp_stack_unwind_one_kernel:327: ret=-5 PC=ffffffffa9383940 SP=ffffbdcfc0b93e68
 0x0 (inexact)

Comment 1 Fedora End Of Life 2017-11-16 19:24:24 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:17:43 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.