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.

Created attachment 477912 [details]
Patch to replace list_for_each_entry with list_for_each_entry_safe in nfs_access_cache_shrinker

Description of problem:
Customer noticed kswapd was getting stuck consuming 100% cpu. Backtraces revealed the culprit to be nfs_access_cache_shrinker. Upstream includes a patch (attached) which corrects a flaw in this function where it uses the wrong list iteration macro to move over the list. It was thus possible for the loop iterator to get "lost" and end up iterating the same now-isolated node over and over forever.

Version-Release number of selected component (if applicable):
kernel 2.6.32-71.el6

I noticed that this is already ON QA as part of BZ 653066.

*** This bug has been marked as a duplicate of bug 653066 ***