Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
After updating dhcp package from version 4.1.1-25.P1.el6_2.1 to version 4.1.1-34.P1.el6, dhcprelay started to segfault with following details:
(gdb) run
Starting program: /usr/sbin/dhcrelay -d ares.example.com xerxes.example.com
Internet Systems Consortium DHCP Relay Agent 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth4.997/90:e2:ba:1f:d4:e1
Sending on LPF/eth4.997/90:e2:ba:1f:d4:e1
Listening on LPF/eth4.120/90:e2:ba:1f:d4:e1
Sending on LPF/eth4.120/90:e2:ba:1f:d4:e1
Listening on LPF/eth4.104/90:e2:ba:1f:d4:e1
Sending on LPF/eth4.104/90:e2:ba:1f:d4:e1
Listening on LPF/eth4.103/90:e2:ba:1f:d4:e1
Sending on LPF/eth4.103/90:e2:ba:1f:d4:e1
Listening on LPF/eth4.102/90:e2:ba:1f:d4:e1
Sending on LPF/eth4.102/90:e2:ba:1f:d4:e1
Listening on LPF/eth4.101/90:e2:ba:1f:d4:e1
Sending on LPF/eth4.101/90:e2:ba:1f:d4:e1
Listening on LPF/eth4.100/90:e2:ba:1f:d4:e1
Sending on LPF/eth4.100/90:e2:ba:1f:d4:e1
Listening on LPF/eth1.998/90:e2:ba:1f:d4:85
Sending on LPF/eth1.998/90:e2:ba:1f:d4:85
Listening on LPF/eth1.2/90:e2:ba:1f:d4:85
Sending on LPF/eth1.2/90:e2:ba:1f:d4:85
Listening on LPF/eth1.12/90:e2:ba:1f:d4:85
Sending on LPF/eth1.12/90:e2:ba:1f:d4:85
Listening on LPF/eth1.11/90:e2:ba:1f:d4:85
Sending on LPF/eth1.11/90:e2:ba:1f:d4:85
Listening on LPF/eth0/00:22:b0:00:0b:a9
Sending on LPF/eth0/00:22:b0:00:0b:a9
Listening on LPF/eth1/90:e2:ba:1f:d4:85
Sending on LPF/eth1/90:e2:ba:1f:d4:85
Listening on LPF/eth4/90:e2:ba:1f:d4:e1
Sending on LPF/eth4/90:e2:ba:1f:d4:e1
Listening on LPF/eth3/90:e2:ba:1f:d4:81
Sending on LPF/eth3/90:e2:ba:1f:d4:81
Listening on LPF/eth2/00:40:95:09:3f:8e
Sending on LPF/eth2/00:40:95:09:3f:8e
Sending on Socket/fallback
Forwarded BOOTREQUEST for 00:25:d3:bf:53:cd to 172.30.0.52
Forwarded BOOTREQUEST for 00:25:d3:bf:53:cd to 172.30.0.32
Program received signal SIGSEGV, Segmentation fault.
0x001196b3 in do_relay4 (ip=0x191330, packet=0xbfffe044, length=<value optimized out>, from_port=17408, from=...,
hfrom=0xbffff05a) at dhcrelay.c:660
660 packet->giaddr = ip->addresses[0];
(gdb) bt
#0 0x001196b3 in do_relay4 (ip=0x191330, packet=0xbfffe044, length=<value optimized out>, from_port=17408, from=...,
hfrom=0xbffff05a) at dhcrelay.c:660
#1 0x00122175 in got_one (h=0x191330) at discover.c:1033
#2 0x0015255e in omapi_one_dispatch (wo=0x0, t=0x0) at dispatch.c:520
#3 0x00123d10 in dispatch () at dispatch.c:92
#4 0x00117c2e in main (argc=4, argv=0xbffff5b4) at dhcrelay.c:549
Version-Release number of selected component (if applicable):
working versions:
[root@router ~]# rpm -qa | grep dhc
dhcp-common-4.1.1-25.P1.el6_2.1.i686
dhcp-4.1.1-25.P1.el6_2.1.i686
dhclient-4.1.1-25.P1.el6_2.1.i686
segfaulting version:
[root@router ~]# rpm -qa | grep dhc
dhcp-common-4.1.1-34.P1.el6.centos.i686
dhcp-4.1.1-34.P1.el6.centos.i686
dhclient-4.1.1-34.P1.el6.centos.i686
How reproducible:
once the DHCP request is received by DHCRelay agent.
Additional info:
Yes, it looks like same problem for me. I am using VLAN interfaces where native VLAN interface (==physical interface) is without an IPv4 address. Thank you for update.