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.

Hello,

there was revealed some new defects in mdadm-3.2.3-7 (compared against
mdadm-3.2.3-6).

1. Resource leak on mdadm-3.2.3/super-intel.c:5687

   variable 'dir' is not freed.

2. (low prio) calling 'close(-1);' on mdadm-3.2.3/super-intel.c:4355

   I'm reporting this even if this should be empty operation.  This situation
   may occur eg. on line 4327 when jumping to error (dfd set to negative
   value).

I'm attaching list of added defects in mdadm-3.2.3-7.

Devel:
  Those errors are mentioned just as a warning and it depends on you whether
  they will be fixed.  These defects can be not so dangerous and/or not so
  prioritized to be fixed in 6.3 so feel free to move it to 6.4 or close it as
  a NOTABUG if we don't need to fix these at all.

Quality engineering:
  This issues were found by static analysis tool and we can't provide any
  reproducer for these.  We are able to rescan package once these problems are
  fixed.  Please check these tests as SanityOnly (just check that patches for
  the issues and check if nothing unexpected was added by the commit).  If you
  want to check the new package with Coverity yourself, feel free to use
  covscan tool (https://engineering.redhat.com/trac/CoverityScan/wiki/covscan).

Pavel

Created attachment 580509 [details]
List of added defects in mdadm-3.2.3-7

Created attachment 580510 [details]
List of all defects in mdadm-3.2.3-7

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.

Hi,

I have pushed patches upstream for these two issues. We may fix the resource
leak in the 6.4 update, I don't think it's serious enough to warrant a 6.3
blocker.

Thanks for reporting these!

Jes

The two listed issues have been addressed by the update to mdadm-3.2.5
in RHEL6.4.

Closing

Jes