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:
If the user loads new table with bigger (and valid, e.g new_size % 4K = 0) physical size directly though dmsetup without growing the device under, there is $subject spam for each block out of range. 

Version-Release number of selected component (if applicable):
kernel-4.18.0-107.el8.x86_64
kmod-kvdo-6.2.1.102-53.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. vdo create --name vdo --device /dev/sda
2. dmsetup table
vdo: 0 19487242776 vdo V2 /dev/disk/by-id/scsi-35000cca26c1a0a38 2441609216 4096 32768 16380 on auto vdo maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1
3. dmsetup reload vdo --table '0 19487242776 vdo V2 /dev/disk/by-id/scsi-35000cca26c1a0a38 3260809216 4096 32768 16380 on auto vdo maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1'
4. dmsetup resume vdo

Actual results:
This messages in syslog for each extra nonexistent block
Jul 24 18:43:07 storageqe-90 kernel: sda: rw=1, want=26086226272, limit=19532873728
Jul 24 18:43:07 storageqe-90 kernel: attempt to access beyond end of device

Expected results:
kvdo does not try to access beyond end of device

Additional info:

Mass migration to Filip.

I've been unable to reproduce this on our systems (RHEL8.2, 4.18.0-187.el8.x86_64). device mapper catches the error and fails the reload before the kvdo module ever sees it, with this message in system logs: "device-mapper: table: 253:3: dm-2 too small for target: start=0, len=534757384, dev_size=534757376". Is the problem reproducible for you?

Verified with kmod-kvdo-6.2.4.26-75.el8.

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 (kmod-kvdo bug fix and enhancement update), 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-2021:1588