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:
numactl bus error while using the --touch
Version-Release number of selected component (if applicable):
numactl-2.0.12-5.el7.x86_64
numactl-2.0.12-3.el7_7.1.x86_64
How reproducible:
always
Steps to Reproduce:
1,
version 2.0.12-4.el7
[root@ci-vm-10-0-136-119 ~]# numactl --length=10GB --file /dev/shm/data1 --interleave=all --touch
ftruncate: Invalid argument
Segmentation fault
2,
version with bugfix for BZ#1763628
numactl-2.0.12-3.el7_7.1.x86_64
[root@ci-vm-10-0-136-119 ~]# numactl --length=10GB --file /dev/shm/data1 --interleave=all --touch
Bus error
[root@ci-vm-10-0-136-119 ~]# echo $?
135
Actual results:
the interesting is that it returns more type of errors depends on size of length:
low mem machine:
No ERROR:
[root@ci-vm-10-0-136-119 ~]# numactl --length=100M --file /dev/shm/data1 --interleave=all --touch
ERROR:
[root@ci-vm-10-0-136-119 ~]# numactl --length=10000M --file /dev/shm/data1 --interleave=all --touch
Bus error
bigger ERROR:
[root@ci-vm-10-0-136-119 ~]# numactl --length=10000000G --file /dev/shm/data1 --interleave=all --touch
numactl: shm mmap: Cannot allocate memory
and the biggest ERROR:
[root@ci-vm-10-0-136-119 ~]# numactl --length=1000000000000000G --file /dev/shm/data1 --interleave=all --touch
ftruncate: Invalid argument
numactl: shm mmap: Cannot allocate memory
free
total used free shared buff/cache available
Mem: 1882036 149744 235092 949744 1497200 623104
Expected results:
no errors
Additional info: