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.
DescriptionBill Nottingham
2011-03-05 00:45:14 UTC
Description of problem:
open-iscsi-2.0-872-rc4-bnx2i/utils/fwparam_ibft/fwparam_ppc.c
This generates a list of network devices by searching openfirmware and sorting them into a 'niclist' array. It then searches for the boot dev path and does:
for (ndx = 0; ndx < nic_count; ndx++) {
if (!strcmp(niclist[ndx], ofwdev->dev_path)) {
snprintf(context->iface, sizeof(context->iface),
"eth%d", ndx);
break;
}
}
Problems:
1) It assumes that the network device will be in the ethX space. While we do not do any renaming out of this namespace by default on ppc, it's possible the administrator may decide to rename devices.
2) It assumes a zero-based, monotonically increasing set of devices (such that the first device is eth0, the second device will be eth1, the third eth2, and so on. Given persistent mappings of device <-> hardware address, hardware swaps & changes in configuration could cause this to not be true, even if every device is in the ethN space.
I may be misunderstanding what this is doing, feel free to correct me.
Version-Release number of selected component (if applicable):
iscsi-initiator-utils-6.2.0.872-17.el6
How reproducible:
Have not attempted to reproduce in the wild; this was done by code inspection.
I think you are right, but I am not that familiar with ppc. The patch came from IBM. I will check out a box and play around some to verify.
Comment 3RHEL Program Management
2011-04-04 02:09:13 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 7RHEL Program Management
2012-05-03 04:36:48 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Description of problem: open-iscsi-2.0-872-rc4-bnx2i/utils/fwparam_ibft/fwparam_ppc.c This generates a list of network devices by searching openfirmware and sorting them into a 'niclist' array. It then searches for the boot dev path and does: for (ndx = 0; ndx < nic_count; ndx++) { if (!strcmp(niclist[ndx], ofwdev->dev_path)) { snprintf(context->iface, sizeof(context->iface), "eth%d", ndx); break; } } Problems: 1) It assumes that the network device will be in the ethX space. While we do not do any renaming out of this namespace by default on ppc, it's possible the administrator may decide to rename devices. 2) It assumes a zero-based, monotonically increasing set of devices (such that the first device is eth0, the second device will be eth1, the third eth2, and so on. Given persistent mappings of device <-> hardware address, hardware swaps & changes in configuration could cause this to not be true, even if every device is in the ethN space. I may be misunderstanding what this is doing, feel free to correct me. Version-Release number of selected component (if applicable): iscsi-initiator-utils-6.2.0.872-17.el6 How reproducible: Have not attempted to reproduce in the wild; this was done by code inspection.