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 1694073 [details]
Patch including a check for curstat being a valid pointer

Hi Divya,

I think this is the same issue fixed by upstream commit c22151f463e3e2494850210444a69948dc0fbdd6 ... this was introduced as the very last change in 1818710 - is it possible the customer didn't have a build with that change?  I don't see an explicit mention of it in the BZ, but do recall this was added to the most recent RHEL 7.9 build and us discussing it on IRC.

That commit provides a less invasive fix than the attached patch I think.

cheers.

I checked in the upstream code base and commit c22151f463e3e2494850210444a69948dc0fbdd6 went in on May 19th, whereas I did a test build for customer on May 18th, so yes this one was missed in the last build packages I provided to customer. Sorry about the confusion here. I'll initiate another build in sometime including the mentioned commit here and discard the fix I mentioned here as your fix is more inclusive and neat. 

IMHO, having the commit mentioned on the bz #1818710, will also be useful for future reference.

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