Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2188394 - mtr coredump when using '-r' option
Summary: mtr coredump when using '-r' option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mtr
Version: 38
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-20 15:28 UTC by Francisco Garcia
Modified: 2023-04-30 01:35 UTC (History)
5 users (show)

Fixed In Version: mtr-0.95-5.fc38 mtr-0.95-5.fc36 mtr-0.95-5.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-24 02:47:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Francisco Garcia 2023-04-20 15:28:46 UTC
mtr crashes when used with the '-r' option, as seen below.

[root@fedora38 ~]# time mtr -r www.google.com -c 1 
Start: 2023-04-20T15:12:55+0000
*** buffer overflow detected ***: terminated
Aborted (core dumped)

real	0m7.690s


[root@fedora38 var]# coredumpctl dump 1563 --output /tmp/core.output
           PID: 1563 (mtr)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Thu 2023-04-20 15:25:28 UTC (1min 41s ago)
  Command Line: mtr -r 127.0.0.1 -c 1
    Executable: /usr/sbin/mtr
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 (fedora)
       Boot ID: 906a62c7633e4417832a6d7c9ebab684
    Machine ID: 9cde4b5d9a734fedbc4600830f99dcc3
      Hostname: fedora38
       Storage: /var/lib/systemd/coredump/core.mtr.0.906a62c7633e4417832a6d7c9ebab684.1563.1682004328000000.zst (present)
  Size on Disk: 46.4K
       Package: mtr/0.95-4.fc38
      build-id: f161d1ee19f2831266e2dfb85860fb52a26eccf8
       Message: Process 1563 (mtr) of user 0 dumped core.
                
                Module libtinfo.so.6 from rpm ncurses-6.4-3.20230114.fc38.x86_64
                Module libncurses.so.6 from rpm ncurses-6.4-3.20230114.fc38.x86_64
                Module libjansson.so.4 from rpm jansson-2.13.1-6.fc38.x86_64
                Module mtr from rpm mtr-0.95-4.fc38.x86_64
                Stack trace of thread 1563:
                #0  0x00007f5a12117b94 __pthread_kill_implementation (libc.so.6 + 0x8eb94)
                #1  0x00007f5a120c6aee raise (libc.so.6 + 0x3daee)
                #2  0x00007f5a120af87f abort (libc.so.6 + 0x2687f)
                #3  0x00007f5a120b060f __libc_message.cold (libc.so.6 + 0x2760f)
                #4  0x00007f5a121abb29 __fortify_fail (libc.so.6 + 0x122b29)
                #5  0x00007f5a121aa364 __chk_fail (libc.so.6 + 0x121364)
                #6  0x00007f5a121a9f45 __snprintf_chk (libc.so.6 + 0x120f45)
                #7  0x000055b0e658fe44 report_close (mtr + 0xae44)
                #8  0x000055b0e658a94f main (mtr + 0x594f)
                #9  0x00007f5a120b0b4a __libc_start_call_main (libc.so.6 + 0x27b4a)
                #10 0x00007f5a120b0c0b __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27c0b)
                #11 0x000055b0e658c125 _start (mtr + 0x7125)
                ELF object binary architecture: AMD x86-64


Reproducible: Always

Comment 1 Tomas Jonsson 2023-04-20 20:39:03 UTC
Something I also noticed is:

mtr -rx google.com / No crash
mtr -xr google.com / Crash

So the bug also depends on:
1, Which order the flags are in
2, If you add a formatting flag, like -j or -x, there is a way to not get mtr to crash when the -r flag is provided. (You just have to add the flags in the correct order)

Comment 2 Robert Scheck 2023-04-21 20:16:09 UTC
Forwarded/reported to upstream: https://github.com/traviscross/mtr/issues/469

Comment 4 Fedora Update System 2023-04-21 21:39:43 UTC
FEDORA-2023-681c2278af has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-681c2278af

Comment 5 Fedora Update System 2023-04-21 21:39:44 UTC
FEDORA-2023-d4f9a6f6f5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d4f9a6f6f5

Comment 6 Fedora Update System 2023-04-21 21:39:45 UTC
FEDORA-2023-6ff427a7d3 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ff427a7d3

Comment 7 Fedora Update System 2023-04-22 01:39:50 UTC
FEDORA-2023-d4f9a6f6f5 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d4f9a6f6f5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d4f9a6f6f5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2023-04-22 01:41:34 UTC
FEDORA-2023-681c2278af has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-681c2278af`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-681c2278af

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2023-04-22 02:34:36 UTC
FEDORA-2023-6ff427a7d3 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6ff427a7d3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ff427a7d3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2023-04-24 02:47:29 UTC
FEDORA-2023-681c2278af has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2023-04-30 01:23:45 UTC
FEDORA-2023-6ff427a7d3 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2023-04-30 01:35:32 UTC
FEDORA-2023-d4f9a6f6f5 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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