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:

  The recv() manpage also covers recvfrom() and recvmsg().  Where it discusses
the "flags" argument (which is present in all three calls) it says:
"The flags argument to a recv() call"... and leaves the other two undefined.


Version-Release number of selected component (if applicable):
  Red Hat Enterprise Linux Workstation release 7.2 Beta (Maipo)


How reproducible:
  100%

Steps to Reproduce:
1. man recvmsg
2.
3.

Actual results:

"The flags argument to a recv() call"


Expected results:

"The flags argument"...  is what the Fedora 22 manpage has; seems reasonable.


Additional info:

  RHEL 4 had a separate manpage [ recvmsg(P) ] which pretty much follows the
POSIX http://pubs.opengroup.org/onlinepubs/009695399/functions/recvmsg.html

Both have slightly conflicting information:  The MSG_WAITALL/SOCK_STREAM
behaviour specified in the "flags" section says it waits for the complete
request - but later (2 paras., dealing with return value) says it returns
"as soon as" without making a MSG_WAITALL exception.

You have to assume the flag-specific behaviour takes precedence, but a lawyer
could easily argue the point.

Created attachment 1130819 [details]
Proposed patch

This problem was already fixed by upstream man-pages commit 4dad515699179f21facd766b9247b955183cffc2 back in Feb 2014.

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-2016-2485.html