Bug 2031143

Summary: segfault in lttng 2.13 when .NET tries to use it
Product: [Fedora] Fedora Reporter: Omair Majid <omajid>
Component: lttng-ustAssignee: Yannick Brosseau <yannick.brosseau>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: ctubbsii, dmarlin, ktdreyer, mjeanson, ramkrsna, suchakra, tdeseyn, yannick.brosseau
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 19:14:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Omair Majid 2021-12-10 15:28:52 UTC
Description of problem:

When .NET tries to use lttng-ust on Rawhide, there's a crash in lttng-ust code:

  * frame #0: 0x00007f8885a47b82 liblttng-ust.so.1`check_event_provider + 162
    frame #1: 0x00007f8885a4d4d1 liblttng-ust.so.1`lttng_ust_probe_register + 33
    frame #2: 0x00007f8885b007b5 libcoreclrtraceptprovider.so`lttng_ust__events_init__DotNETRuntime() at ust-tracepoint-event.h:1198:14
    frame #3: 0x00007f888683fa2e ld-linux-x86-64.so.2`call_init(l=<unavailable>, argc=10, argv=0x00007ffcd00cfd88, env=0x00007ffcd00cfde0) at dl-init.c:70:3
    frame #4: 0x00007f888683fb1c ld-linux-x86-64.so.2`_dl_init(main_map=0x0000556bd608a290, argc=10, argv=0x00007ffcd00cfd88, env=0x00007ffcd00cfde0) at dl-init.c:117:5
    frame #5: 0x00007f88864534c5 libc.so.6`_dl_catch_exception + 229
    frame #6: 0x00007f88868437de ld-linux-x86-64.so.2`dl_open_worker at dl-open.c:821:5
    frame #7: 0x00007f8886453468 libc.so.6`_dl_catch_exception + 136
    frame #8: 0x00007f8886843b5c ld-linux-x86-64.so.2`_dl_open at dl-open.c:896:17
    frame #9: 0x00007f888638294c libc.so.6`dlopen_doit + 92
    frame #10: 0x00007f8886453468 libc.so.6`_dl_catch_exception + 136
    frame #11: 0x00007f8886453533 libc.so.6`_dl_catch_error + 51
    frame #12: 0x00007f888638244e libc.so.6`_dlerror_run + 142
    frame #13: 0x00007f88863829d8 libc.so.6`dlopen.5 + 72
    frame #14: 0x00007f8885fd6893 libcoreclr.so`PAL_InitializeTracing() at tracepointprovider.cpp:116:9
    frame #15: 0x00007f888683fa2e ld-linux-x86-64.so.2`call_init(l=<unavailable>, argc=10, argv=0x00007ffcd00cfd88, env=0x00007ffcd00cfde0) at dl-init.c:70:3
    frame #16: 0x00007f888683fb1c ld-linux-x86-64.so.2`_dl_init(main_map=0x0000556bd6060050, argc=10, argv=0x00007ffcd00cfd88, env=0x00007ffcd00cfde0) at dl-init.c:117:5
    frame #17: 0x00007f88864534c5 libc.so.6`_dl_catch_exception + 229
    frame #18: 0x00007f88868437de ld-linux-x86-64.so.2`dl_open_worker at dl-open.c:821:5
    frame #19: 0x00007f8886453468 libc.so.6`_dl_catch_exception + 136
    frame #20: 0x00007f8886843b5c ld-linux-x86-64.so.2`_dl_open at dl-open.c:896:17
    frame #21: 0x00007f888638294c libc.so.6`dlopen_doit + 92
    frame #22: 0x00007f8886453468 libc.so.6`_dl_catch_exception + 136
    frame #23: 0x00007f8886453533 libc.so.6`_dl_catch_error + 51
    frame #24: 0x00007f888638244e libc.so.6`_dlerror_run + 142
    frame #25: 0x00007f88863829d8 libc.so.6`dlopen.5 + 72
    frame #26: 0x00007f8886274ead libhostpolicy.so`pal::load_library(path="/home/tmds/rpmbuild/BUILD/dotnet-9e8b04bbff820c93c142f99a507a46b976f5c14c-x64-bootstrap/src/aspnetcore.ae1a6cbe225b99c0bf38b7e31bf60cb653b73a52/artifacts/source-build/self/package-cache/microsoft.netcore.app.crossgen2.linux-x64/6.0.0/tools/libcoreclr.so", dll=0x00007f888629e0a0) at pal.unix.cpp:230:12

Please see the upstream issue tracker for complete details:

https://bugs.lttng.org/issues/1339

This crash only happens on rawhide.

I believe this is the final fix lttng-ust ended up applying, but the package maintainer in Fedora is probably in a better position to judge this: https://bugs.lttng.org/projects/lttng-ust/repository/lttng-ust/revisions/05bfa3dc3a6e6b2ece3686a5f384b6645c2a5010

Could we add a fix for this to Rawhide?

Comment 1 Michael Jeanson 2021-12-10 16:23:28 UTC
I spoke with the maintainer of lttng-ust and a new point release of 2.13 including
the patches for the dotnet issue will happen today. I should then be able to
update the package in rawhide before the end of the day.

Regards,

Michael

Comment 2 Omair Majid 2021-12-10 20:41:25 UTC
That sounds great. Thanks for sorting this out so quickly!

Comment 3 Michael Jeanson 2021-12-10 21:18:19 UTC
I pushed a new build with the fixes :

https://koji.fedoraproject.org/koji/taskinfo?taskID=79806667

Once it lands in rawhide, the dotnet package that builds UST probe providers
will need to be rebuilt against this fixed lttng-ust package.

Comment 4 Ben Cotton 2022-02-08 21:21:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 5 Christopher Tubbs 2022-05-16 06:34:13 UTC
Would this issue be related to the error message I got upgrading to F36:

Error: 
 Problem: conflicting requests
  - nothing provides liblttng-ust.so.0()(64bit) needed by workspacesclient-3.1.9.1245-2.x86_64
(try to add '--skip-broken' to skip uninstallable packages)


Or is that an unrelated issue? I've been using Amazon WorkSpaces RPM, which was a DEB, but was converted to an RPM using alien. This worked fine in F35, but has the dependency problem above. I'm trying to figure out if this is solvable at all in F36, or if I'm just not going to be able to use Amazon WorkSpaces Linux client at all in F36.

Comment 6 Michael Cronenworth 2022-06-15 19:59:29 UTC
Christopher, the error you are seeing is because the upstream dotnet nuget package has a copy of 'libcoreclrtraceptprovider.so' compiled against an older liblttng-ust.

nuget package: microsoft.netcore.app.runtime.linux-x64

This gets pulled in and used when you compile a dotnet app instead of using the system runtime libraries. May be worth filing a bug against donet, but it may not be a bug. In any case the behavior should be reviewed.

Amazon would have to package up a Fedora specific RPM to fix it for you.

Comment 7 Michael Cronenworth 2022-06-16 04:05:23 UTC
Upstream report: https://github.com/dotnet/runtime/issues/57784

Comment 8 Ben Cotton 2023-04-25 16:46:43 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 9 Ludek Smid 2023-05-25 19:14:37 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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