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 1218333 [details]
collection of upstream patches needed to better support ZFS

Description of problem:
Though we don't support it as a file system, LLNL uses ZFS and there are several upstream patches which are needed to properly identify it and report correctly when we come across ZFS partitions. 

All of these patches are upstream and together they fix the 7.3 util-linux to work with  LLNL's ZFS partitions.

All of the patches with one exception only touch the ZFS support so they should not affect other users. 102 is the one exception and it fixes a potential buffer overflow overflow in the core code. I submitted a separate bug for that because of this. However, I kept it in this patch set since it might make it easier to accept.

See BZ#1392656

BTW I just noticed a minor typo in my text. What I meant to say is:

...it might make it easier to apply.

Note that the patch "libblkid: fix potential bufer overflows" has been applied to fix bug #1392656.

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