Description of problem:
When setting up for file based access to a VDO's backing device, the file name is copied into a buffer via strcpy(). That buffer is allocated 1 byte too small to contain the terminating \0.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run any VDO user tool under valgrind.
Valgrind reports: "Invalid write of size 1"
Valgrind does not report any invalid writes.
To date, we have seen no consequences from this issue.
Verified with vdo-18.104.22.168-14.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.