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:
- Unless we're doing this wrong, if you try to resolve a path under a chrooted environment, it goes into an infinite loop that crashes the script with a MAXACTION safety check.

Version-Release number of selected component (if applicable):
- systemtap-3.0-7.el7.x86_64

How reproducible:

Reproducer - look up a process working directory:
$ sudo stap -e 'probe kprocess.exit {t=task_current(); println(task_dentry_path(t, @cast(t, "task_struct")->fs->pwd->dentry,@cast(t,"task_struct")->fs->pwd->mnt))}' -c 'perl -e "chroot(qw(/tmp))"'
ERROR: MAXACTION exceeded near identifier 'real_mount' at /usr/share/systemtap/tapset/linux/dentry.stp:158:10
WARNING: Number of errors: 1, skipped probes: 0
WARNING: /usr/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]

Actual results:
- ERROR: MAXACTION exceeded near identifier 'real_mount' at /usr/share/systemtap/tapset/linux/dentry.stp:158:10

Expected results:


Additional info:

Fixed in upstream commit 6b4d1fc: 

<https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commit;h=6b4d1fcbfa2e9706749cd549ea30df2b67716a0f>

Thanks for the great reproducer. I added it as a test case.

Customer has requested a test package. Is it possible to provide one?

Cusomter has confirmed patch addresses identified issue.

Thanks for letting us know!

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2301