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

+++ This bug was initially created as a clone of Bug #1162711 +++

Description of problem:
commit a4fa582908b9c63957240cb0cb68b59d56244ef5
Author: Bodo Stroesser <bstroesser.com>
Date:   Thu Nov 6 13:26:00 2014 -0500

    write_vc: fix write retry loop for nonblocking mode
    
    This is a simple fix for the write retry loop that is used on
    non-blocking connections if write() failed with -EAGAIN.
    
    Additionally it removes a redundant if () {}
    
    Erroneously at each cycle of the loop the length of the data
    to send is incremented and the buffer pointer is decremented.
    Thus, it might happen that:
    * the application crashes
    * data from the memory before the buffer is sent
    
    Signed-off-by: Bodo Stroesser <bstroesser.com>
    Signed-off-by: Steve Dickson <steved>


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


How reproducible:
100%

Steps to Reproduce:
1.run reproducer

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://rhn.redhat.com/errata/RHBA-2015-0487.html