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.
Created attachment 1218332[details]
upstream patch to address buffer overflow.
LLNL was working on util-linux to fix other issues and found that this upstream patch helped deal with a problem that they were having.
This patch addresses a buffer overflow that could happen and looks right and so it is probably a good idea to pick it up.
(In reply to Ben Woodard from comment #0)
,,,
> LLNL was working on util-linux to fix other issues and found that this
> upstream patch helped deal with a problem that they were having.
Ben if you could attach a reproducer or describe how to reproduce the defect so QA can validate the code fix it would be appreciated. Alternatively if LLNL could validate the fix with a Red Hat built package that would work too.
Thank you,
Travis
(In reply to Ben Woodard from comment #4)
> This is an obvious problem which was found through code inspection while
> searching for another problem. The problem and patch are self evident.
I'm confused, you stated in the description:
"... this upstream patch helped deal with a problem that they were having."
That seems to imply that LLNL was experiencing a problem that this patch resolved. If that is the case it also means LLNL has knowledge on how to reproduce the problem. Such knowledge could help QA validate that the fix they implemented resolves the problem for the Red Hat built package which could be different than the package LLNL is running. Not really asking for much here, just a way to reproduce the problem or assistance from LLNL to validate the fix if it isn't something that could be validated here for lack of an HPC environment.
Hi,
I am not sure if I can properly test this.
Do you know about some reproducer or real scenario? Or is the customer able to test this?
If not I will probably do only some sanity testing.
We have been using a local rebuild of util-linux-2.23.2-33.el7 with this patch applied on our production clusters since mid-October. Without the patch, we had issues getting our storage nodes to recognize all of their disks on boot. With the modified util-linux, nodes boot reliably.
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://access.redhat.com/errata/RHBA-2017:2186
Created attachment 1218332 [details] upstream patch to address buffer overflow. LLNL was working on util-linux to fix other issues and found that this upstream patch helped deal with a problem that they were having. This patch addresses a buffer overflow that could happen and looks right and so it is probably a good idea to pick it up.