Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 dmstats create --filemap operation creates statistics regions that map the extents of a file in a file system and groups them together to aggregate statistics for the file.
This fails when the file name contains whitespace characters:
# dmstats create --filemap RHEL\ 8.4\ Clone-disk1.vdi
device-mapper: message ioctl on (253:0) failed: Invalid argument
Could not create regions from file /root/RHEL 8.4 Clone/RHEL 8.4 Clone-disk1.vdi.
free(): double free detected in tcache 2
Aborted (core dumped)
There are two problems here: the message ioctl fails since whitespace is not supported in the stats region aux_data value:
dm message (253:0) [ opencount flush ] @stats_set_aux 0 DMS_GROUP=RHEL 8.4 Clone-disk1.vdi:0-19#- [16384] (*1)
device-mapper: message ioctl on (253:0) failed: Invalid argument
The embedded space causes stats_set_aux value to be treated as three separate arguments: "DMS_GROUP=RHEL", "8.4", "Clone-disk1.vdi:0-19#-"
The double free is then triggered because the dmstats error path destroys the dm_bitmap used to track group members on error, and this is also freed by the later call to dm_stats_destroy for the stats handle used for the operation.
Renaming the file to use '_' instead of space avoids the error:
# dmstats create --filemap RHEL_8.4_Clone-disk1.vdi
RHEL_8.4_Clone-disk1.vdi: Created new group with 4 region(s) as group ID 0.
Version-Release number of selected component (if applicable):
Reproduced on RHEL8, Fedora & current git
device-mapper-1.02.175-9.fc37.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create a file with space characters in the name
2. Attempt to create stats regions with "dmstats create --filemap ..."
Actual results:
Error setting aux data and double free/abort.
Expected results:
dmstats should be able to map the regions of the file.
Additional info:
The file name is stored in aux_data as a group alias for the group of regions that map the file's extents. One way to avoid the problem would be to escape space characters as "\x20" when passing the alias to the stats_set_aux message.
Comment 2RHEL Program Management
2023-09-23 18:50:48 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3RHEL Program Management
2023-09-23 18:55:49 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.