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:
After adding a path with double slash with semanage fcontext the added path doesn't get the wanted context

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

How reproducible:
100%

Steps to Reproduce:
# mkdir /tmp/test
# touch /tmp/test/a
# touch /tmp/test/b
# semanage fcontext -a -t var_log_t "/tmp//test(/.*)?"
# restorecon -RvvF /tmp/test/
(nothing happens)
# ll -Z /tmp/test/a 
-rw-r--r--. root root unconfined_u:object_r:user_tmp_t:s0 /tmp/test/a
  
Actual results:
Double slash paths are invalid

Expected results:
Semanage should convert directly subsequent slashes to one slash only, or work well with more directly subsequent slashes 

Additional info:

That is someone tough to do. I guess we could do a realpath on /tmp//test somehow if we can figure out where the path get screwed up.

/tmp/../test(/.*)?

IE There are a lot of paths that regex will not complain about, but this is somewhat the problem of the user.  Currently the tool is checking for spaces so we could add "//" as being invalid, I am not sure what else we should look for,

I am going to close this one for now as CANTFIX. Let's look if we can find a solution in Fedora first.