Description of problem:

If /boot is on an xfs filesystem, and the directory contains a hole in the extent allocation, booting fails with "error: not a correct xfs inode"

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

2.02-142.el8_7.3.x86_64

How reproducible:

should be very easy

Steps to Reproduce:

1) have older kernel installed
2) create several hundred files with long names in /boot:

1. for i in {001..300}

   ; do
   touch /boot/filler_filename____________________________________${i}
   done

3) install new kernel version rpms
4) remove the filler files:

1. rm -f /boot/filler_filename*

5) verify that /boot has a hole:

1. xfs_bmap /boot
   boot:
   0: [0..7]: 748422104..748422111
   1: [8..15]: hole
   2: [16..23]: 748422080..748422087

6) reboot

Actual results:

booting fails with "error: not a correct xfs inode"

Expected results:

booting succeeds

Additional info:

bug also affects RHEL 7, but is fixed in RHEL 9