RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1917713 - Segfault in NetworkManager
Summary: Segfault in NetworkManager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-19 09:08 UTC by Maxime Coquelin
Modified: 2021-05-18 13:34 UTC (History)
12 users (show)

Fixed In Version: NetworkManager-1.30.0-0.7.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 13:32:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Coredump (1.10 MB, application/x-lz4)
2021-01-19 09:08 UTC, Maxime Coquelin
no flags Details
sos report (13.46 MB, application/x-xz)
2021-01-19 09:11 UTC, Maxime Coquelin
no flags Details

Description Maxime Coquelin 2021-01-19 09:08:17 UTC
Created attachment 1748657 [details]
Coredump

Description of problem:

NetworkManager segfault when just setting eth0 up.
See attached coredump.

Version-Release number of selected component (if applicable):
NetworkManager-1.30.0-0.3.el8.x86_64

How reproducible:

Only reproduced once.

Steps to Reproduce:
1.
2.
3.

ip l set eth1 down
ip l set eth0 up

Actual results:

[  356.749661] NetworkManager[761]: segfault at 1 ip 00007f13e16a1da1 sp 00007ffc99170138 error 4 in libgobject-2.0.so.0.5600.4[7f13e166d000+51000]
[  356.753307] Code: 85 d5 21 00 48 8b 34 e8 eb b6 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 85 ff 74 47 48 8b 07 48 85 c0 74 3f <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 48 89 c2 0f b6 42 14

Expected results:


Additional info:

Comment 1 Maxime Coquelin 2021-01-19 09:11:08 UTC
Created attachment 1748660 [details]
sos report

Comment 2 Beniamino Galvani 2021-01-19 09:29:23 UTC
Backtrace:

 #0  0x00007f13e16a1da1 in g_type_check_instance_is_fundamentally_a () from /lib64/libgobject-2.0.so.0
 #1  0x00007f13e1682749 in g_object_unref () from /lib64/libgobject-2.0.so.0
 #2  0x000055892af5c36d in nm_g_object_unref (obj=<optimized out>) at ./shared/nm-glib-aux/nm-macros-internal.h:983
 #3  nm_device_get_hostname_from_dns_lookup (self=0x55892ca87dc0, addr_family=addr_family@entry=10,
     out_wait=out_wait@entry=0x7ffc991702c4) at src/devices/nm-device.c:17644
 #4  0x000055892ae1ddb1 in update_system_hostname (self=0x55892c9ff000, msg=<optimized out>) at src/nm-policy.c:949
 #5  0x000055892ae1e7c2 in update_routing_and_dns (self=self@entry=0x55892c9ff000, force_update=force_update@entry=0,
     changed_device=changed_device@entry=0x55892ca59540) at src/nm-policy.c:1268
 #6  0x000055892ae1f15c in device_state_changed (device=0x55892ca59540, new_state=NM_DEVICE_STATE_ACTIVATED,
     old_state=NM_DEVICE_STATE_SECONDARIES, reason=<optimized out>, user_data=0x55892c9ff018) at src/nm-policy.c:2058
 #7  0x00007f13dc12209e in ffi_call_unix64 () from /lib64/libffi.so.6
 #8  0x00007f13dc121a4f in ffi_call () from /lib64/libffi.so.6
 #9  0x00007f13e167dec5 in g_cclosure_marshal_generic () from /lib64/libgobject-2.0.so.0
 #10 0x00007f13e167d3fd in _g_closure_supports_invoke_va () from /lib64/libgobject-2.0.so.0
 #11 0x0000000000000000 in ?? ()

Comment 9 errata-xmlrpc 2021-05-18 13:32:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: NetworkManager and libnma security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1574


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