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.
Prior to this update, the iproute utility handled the return values of the send() system call incorrectly when reading kernel responses. Consequently, iproute could interpret successful kernel responses as failures, which caused iproute to terminate with an error. With this update, iproute uses the return values correctly and processes kernel responses as intended.
Description of problem:
iproute2 was fixed incorrectly by iproute2-2.6.32-rtnl_send-hang.patch
--- a/ip/iplink.c
+++ b/ip/iplink.c
@@ -158,8 +158,8 @@ static int iplink_have_newlink(void)
req.n.nlmsg_type = RTM_NEWLINK;
req.i.ifi_family = AF_UNSPEC;
- rtnl_send(&rth, (char *)&req.n, req.n.nlmsg_len);
- rtnl_listen(&rth, accept_msg, NULL);
+ if (rtnl_send(&rth, &req.n, req.n.nlmsg_len) == 0)
+ rtnl_listen(&rth, accept_msg, NULL);
}
return have_rtnl_newlink;
}
Look at the rtnl_send() function
int rtnl_send(struct rtnl_handle *rth, const char *buf, int len)
{
return send(rth->fd, buf, len, 0);
}
send() returns the number of bytes sent, so with these patch we leave a response in a socket. Each next command will get a response for a previous command.
I think we must check that rtnl_send() returns a positive value.
Version-Release number of selected component (if applicable):
iproute-2.6.32-31.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Install old kernel (2.6.18)
2. # ip link set up dev eth0
RTNETLINK answers: Operation not supported
Actual results:
Can't bring a network interface up
Expected results:
It works fine w/o this patch
Additional info:
Upstream is still working on fix. Current upstream sources does not provide complete fix.
I recommend to apply my patch or the latter version posted in referenced mailing list which adds a warning to error output.
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, 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://rhn.redhat.com/errata/RHBA-2015-1331.html
Description of problem: iproute2 was fixed incorrectly by iproute2-2.6.32-rtnl_send-hang.patch --- a/ip/iplink.c +++ b/ip/iplink.c @@ -158,8 +158,8 @@ static int iplink_have_newlink(void) req.n.nlmsg_type = RTM_NEWLINK; req.i.ifi_family = AF_UNSPEC; - rtnl_send(&rth, (char *)&req.n, req.n.nlmsg_len); - rtnl_listen(&rth, accept_msg, NULL); + if (rtnl_send(&rth, &req.n, req.n.nlmsg_len) == 0) + rtnl_listen(&rth, accept_msg, NULL); } return have_rtnl_newlink; } Look at the rtnl_send() function int rtnl_send(struct rtnl_handle *rth, const char *buf, int len) { return send(rth->fd, buf, len, 0); } send() returns the number of bytes sent, so with these patch we leave a response in a socket. Each next command will get a response for a previous command. I think we must check that rtnl_send() returns a positive value. Version-Release number of selected component (if applicable): iproute-2.6.32-31.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install old kernel (2.6.18) 2. # ip link set up dev eth0 RTNETLINK answers: Operation not supported Actual results: Can't bring a network interface up Expected results: It works fine w/o this patch Additional info: