Bug 2216131

Summary: the lldptool program segfaults after entering the quit command
Product: Red Hat Enterprise Linux 8 Reporter: Milos Malik <mmalik>
Component: lldpadAssignee: Aaron Conole <aconole>
Status: CLOSED MIGRATED QA Contact: Matt Lucius <malucius>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.9CC: kzhang
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 10:51:36 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 Milos Malik 2023-06-20 08:55:23 UTC
Description of problem:

Version-Release number of selected component (if applicable):
lldpad-1.0.1-19.git036e314.el8.x86_64

How reproducible:
 * always

Steps to Reproduce:
1. get a RHEL-8.9 machine
2. start the lldpad service
3. run the lldptool program
4. write the quit word and hit the enter key

Actual results:
# service lldpad start
Redirecting to /bin/systemctl start lldpad.service
# service lldpad status
Redirecting to /bin/systemctl status lldpad.service
ā— lldpad.service - Link Layer Discovery Protocol Agent Daemon.
   Loaded: loaded (/usr/lib/systemd/system/lldpad.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2023-06-20 04:52:28 EDT; 3s ago
 Main PID: 7750 (lldpad)
    Tasks: 1 (limit: 11126)
   Memory: 280.0K
   CGroup: /system.slice/lldpad.service
           └─7750 /usr/sbin/lldpad -t

Jun 20 04:52:28 ci-vm-10-0-137-46.hosted.upshift.rdu2.redhat.com systemd[1]: Started Link Layer D…..
Hint: Some lines were ellipsized, use -l to show in full.
# lldptool
lldptool v1.1.0
Copyright (c) 2007-2010, Intel Corporation

Substantially modified from:  hostapd_cli v 0.5.7
Copyright (c) 2004-2007, Jouni Malinen <j> and contributors

This program is free software. You can distribute it and/or modify it
under the terms of the GNU General Public License version 2.




Interactive mode

> quit
Segmentation fault (core dumped)
# echo $?
139
# coredumpctl info -1
           PID: 7762 (lldptool)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Tue 2023-06-20 04:52:47 EDT (11s ago)
  Command Line: lldptool
    Executable: /usr/sbin/lldptool
 Control Group: /user.slice/user-0.slice/session-4.scope
          Unit: 
         Slice: user-0.slice
       Session: 4
     Owner UID: 0 (root)
       Boot ID: 8328d66f57934493b67c0bbefc07554b
    Machine ID: 57da1e1c05ad4c59a192c7c459f0125c
      Hostname: localhost
       Storage: /var/lib/systemd/coredump/core.lldptool.0.8328d66f57934493b67c0bbefc07554b.7762.1687251167000000.lz4
       Message: Process 7762 (lldptool) of user 0 dumped core.
                
                Stack trace of thread 7762:
                #0  0x00007f516d7db165 _dl_close (ld-linux-x86-64.so.2)
                #1  0x00007f516cf4c9d4 _dl_catch_exception (libc.so.6)
                #2  0x00007f516cf4ca93 _dl_catch_error (libc.so.6)
                #3  0x00007f516d5d152e _dlerror_run (libdl.so.2)
                #4  0x00007f516d5d10b8 dlclose (libdl.so.2)
                #5  0x000055df8a9db970 close_history (lldptool)
                #6  0x000055df8a9d0aa3 main (lldptool)
                #7  0x00007f516ce1ed85 __libc_start_main (libc.so.6)
                #8  0x000055df8a9d0aee _start (lldptool)
#

Expected results:
 * no segfaults

Comment 1 RHEL Program Management 2023-09-21 10:16:17 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 10:51:36 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.