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.

Description of problem:
The lseek system call for SEEK_HOLE can report an incorrect size for a hole at the end of a file.  (This doesn't affect reads or writes.)

Version-Release number of selected component (if applicable):
All RHEL9.

How reproducible:
No reproducer (the upstream reproducer doesn't trigger on RHEL9), but we should be able to create one.

Additional info:

Upstream fix:
  f3506eee81d1  gfs2: Fix length of holes reported at end-of-file

It turns out that the bug that commit f3506eee81d1 fixes is only visible at the filesystem / kernel trace point level; the lseek and FS_IOC_FIEMAP ioctl syscalls hide this filesystem misbehavior.  I don't think a test case based on 'perf trace' would be very useful; please let me know if you think otherwise.

Regression tests passed with kernel-5.14.0-54.mr242_220204_1900.el9.x86_64

Regression tests passed with kernel-5.14.0-70.2.1.el9_0.x86_64

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 (new packages: kernel), 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-2022:3907