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.
If the "ip" command was used to create a veth device pair, and the "peer" parameter was specified but the "name" parameter was not used, a segmentation fault occurred. The "name" parameter was an unnecessary requirement for this operation. The need for this parameter has been removed and the command now works as expected.
Created attachment 449276[details]
patch for ip command to resolve segfault with incomplete veth options
Description of problem:
If the ip command is used to create a veth device pair, and the "peer" option is specified but no "name" is given, a segfault will occur.
Version-Release number of selected component (if applicable):
Multiple (including latest upstream), including: iproute-2.6.32-9.el6.i686
How reproducible:
Always
Steps to Reproduce:
1. # ip link add link eth0 type veth peer
2.
3.
Actual results:
# ip link add link eth0 type veth peer
Segmentation fault (core dumped)
Expected results:
No segfault.
Additional info:
Patch is attached, and has been sent to upstream maintainer as well.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
If the "ip" command was used to create a veth device pair, and the "peer" parameter was specified but the "name" parameter was not used, a segmentation fault occurred. The "name" parameter was an unnecessary requirement for this operation. The need for this parameter has been removed and the command now works as expected.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0757.html
Created attachment 449276 [details] patch for ip command to resolve segfault with incomplete veth options Description of problem: If the ip command is used to create a veth device pair, and the "peer" option is specified but no "name" is given, a segfault will occur. Version-Release number of selected component (if applicable): Multiple (including latest upstream), including: iproute-2.6.32-9.el6.i686 How reproducible: Always Steps to Reproduce: 1. # ip link add link eth0 type veth peer 2. 3. Actual results: # ip link add link eth0 type veth peer Segmentation fault (core dumped) Expected results: No segfault. Additional info: Patch is attached, and has been sent to upstream maintainer as well.