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.
Description of problem:
If a read/write occurs while a signal is delivered to corosync, the signal could interrupt the read/write operation. Hunt down all read/write operations in corosync of fixed length and add mechanism to handle interrupted read/write system calls.
Version-Release number of selected component (if applicable):
corosync-1.2.3
How reproducible:
theoretical problem, could be cause of ring id file being zero.
Steps to Reproduce:
1. none known
2.
3.
Actual results:
read and write operations on files read or write may only return partial read or partial write.
Expected results:
read or write operations should return full length of read/write even when signals interrupt the operation.
Additional info:
Reading signal(7) man page isn't very clear about restarts (it says disks do not count as "slow medium" and don't return EINTR if interrupted with SIGACTION but other mediums do.
I wrote a test case attached which verifies this manpage behavior with 1gb of reads couldn't get a short read operation. It says this may be linux specific, so if people report this in the future on other platforms we can reopen.