This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2211329 - Typo 'iterlave' in memhog man page [rhel8]
Summary: Typo 'iterlave' in memhog man page [rhel8]
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: numactl
Version: 8.9
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Pingfan Liu
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-31 06:33 UTC by Mario Casquero
Modified: 2023-09-25 19:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-25 19:34:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-8745 0 None Migrated None 2023-09-25 19:34:11 UTC
Red Hat Issue Tracker RHELPLAN-158666 0 None None None 2023-05-31 06:34:43 UTC

Description Mario Casquero 2023-05-31 06:33:13 UTC 
Description of problem:
There is a typo at the EXAMPLES section memhog man page:

EXAMPLES
       # Allocate a 1G region, iterleave across nodes 0,1,2,3, repeat test 4 times

'iterleave' has to be changed by 'interleave' which corresponds to the memory policy.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Pingfan Liu 2023-06-12 03:05:22 UTC 
Hi Mario,

Which version do you test against?


Thanks
Comment 2 Mario Casquero 2023-06-12 05:44:30 UTC 
(In reply to Pingfan Liu from comment #1)
> Hi Mario,
> 
> Which version do you test against?
> 
> 
> Thanks
Hello,

With kernel-4.18.0-494.el8.x86_64 and numactl-2.0.12-13.el8.x86_64 it is reproducible.
Comment 3 Pingfan Liu 2023-06-12 09:31:48 UTC 
(In reply to Mario Casquero from comment #2)
> (In reply to Pingfan Liu from comment #1)
> > Hi Mario,
> > 
> > Which version do you test against?
> > 
> > 
> > Thanks
> Hello,
> 
> With kernel-4.18.0-494.el8.x86_64 and numactl-2.0.12-13.el8.x86_64 it is
> reproducible.

It should be fixed at the current release 2.0.16-1. Could you verify it? And if ok, I can close it

Thanks
Comment 4 Mario Casquero 2023-06-12 09:50:27 UTC 
(In reply to Pingfan Liu from comment #3)
> (In reply to Mario Casquero from comment #2)
> > (In reply to Pingfan Liu from comment #1)
> > > Hi Mario,
> > > 
> > > Which version do you test against?
> > > 
> > > 
> > > Thanks
> > Hello,
> > 
> > With kernel-4.18.0-494.el8.x86_64 and numactl-2.0.12-13.el8.x86_64 it is
> > reproducible.
> 
> It should be fixed at the current release 2.0.16-1. Could you verify it? And
> if ok, I can close it
> 
> Thanks

[root@dell-per750-24 kar]# rpm -qa | grep numactl
numactl-devel-2.0.16-1.el8.x86_64
numactl-libs-2.0.16-1.el8.x86_64
numactl-2.0.16-1.el8.x86_64

# Allocate a 1G region, iterleave across nodes 0,1,2,3, repeat test 4 times

Hello Pingfan,

I still see the typo at the examples section of memhog man page.
Comment 5 Pingfan Liu 2023-06-12 12:11:38 UTC 
Oh, I find the typo. I had thought it appeared in the section
"
Supported numa-policies:
.TP
.B interleave
Memory will be allocated using round robin on nodes. When
memory cannot be allocated on the current interleave, target fall back
to other nodes.  Multiple nodes may be specified.
"

But it turned out that I was wrong.

Thanks
Comment 6 RHEL Program Management 2023-09-25 17:50:29 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 7 RHEL Program Management 2023-09-25 19:34:16 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.
Note You need to log in before you can comment on or make changes to this bug.