Bug 1732922 - kernel: attempt to access beyond end of device
Summary: kernel: attempt to access beyond end of device
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Ken Raeburn
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-24 17:42 UTC by Jakub Krysl
Modified: 2020-02-07 17:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Jakub Krysl 2019-07-24 17:42:44 UTC
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:

Comment 1 Jakub Krysl 2019-10-15 14:38:54 UTC
Mass migration to Filip.


Note You need to log in before you can comment on or make changes to this bug.