Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 1900380[details]
simple C program to ignore SIGPIPE, configure stdout buffering, and fwrite a string repeatedly
Description of problem: With line buffering configured on stdout,
and SIGPIPE ignored, fwrite calls to stdout on a broken pipe never report
an error.
Version-Release number of selected component (if applicable):
glibc-2.34-39.el9.x86_64
How reproducible:
always
Steps to Reproduce:
1. Compile and run the attached program fwrite.c
2. fwrite -l hello 5000 | head -n1
3.
Actual results:
The program succeeds in calling fwrite 5000 times to print hello,
even though the writes are actually failing with EPIPE.
Expected results:
The fwrite call should return an error. At some point, ferror starts
returning 1, but fwrite continues to succeed.
Additional info:
I've submitted this upstream to the upstream bug tracker since this behaviour needs to fixed upstream.
When we get a fix upstream then we can consider backporting this into CentOS Stream and RHEL.
I'm going to mark this a CLOSED/USPTREAM and track the bug upstream, we can reopen this for backport when the usptream work is complete.
Created attachment 1900380 [details] simple C program to ignore SIGPIPE, configure stdout buffering, and fwrite a string repeatedly Description of problem: With line buffering configured on stdout, and SIGPIPE ignored, fwrite calls to stdout on a broken pipe never report an error. Version-Release number of selected component (if applicable): glibc-2.34-39.el9.x86_64 How reproducible: always Steps to Reproduce: 1. Compile and run the attached program fwrite.c 2. fwrite -l hello 5000 | head -n1 3. Actual results: The program succeeds in calling fwrite 5000 times to print hello, even though the writes are actually failing with EPIPE. Expected results: The fwrite call should return an error. At some point, ferror starts returning 1, but fwrite continues to succeed. Additional info: