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:
http://marc.info/?l=linux-mm&m=129842655126639&w=2
Per developer:
"patch 1 I for sure. The rest I'm unsure yet. I'm unconvinced following
prev page is better than vma (definitely it was wrong for KSM and in
fact Andi dropped that patch already). Anyway Andi knows NUMA
best. We'll see. Last patch I'm unsure if we can include it until it's
upstream because it becomes API visible.
In some ways we've the same problem with the smaps new line, we've to
wait it to hit mainline before showing the smaps, but that's a minor
issue, and we already showed the anonpages in /proc/meminfo (it got
merged upstream so no problem, but usually apps shouldn't break
because of a newline)."