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 599753 [details]
reproducer

Description of problem:
posix_spawn() executes sh when it can't execute it's argument. This breaks ksh build time tests

Version-Release number of selected component (if applicable):
glibc-2.12-1.84.el6

How reproducible:
always

Steps to Reproduce:
1. gcc -o repr reproducer.c
2. ./repr
3.
  
Actual results:
"ENOEXEC invokes sh"

Expected results:
"ENOEXEC produces exist status 127 => GOOD"

Additional info:
It works in Fedora

Created attachment 602562 [details]
Potential fix

Sorry, but after further technical review, this bug is being closed as WONTFIX.

The fundamental problem is fixing this issue would require an ABI change in glibc.  Effectively we'd have to export a glibc-2.15 ABI, which is not a change suitable for RHEL 6 which utilizes glibc-2.12.  For technical reasons it is not possible to introduce a glibc-2.12.1 ABI.

FWIW this will work correctly in RHEL 7 which uses glibc-2.16.