Bug 1387874

Summary: MSG_FASTOPEN definition missing
Product: Red Hat Enterprise Linux 7 Reporter: Jeremy Harris <jeharris>
Component: glibcAssignee: Patsy Griffin <pfrankli>
Status: CLOSED ERRATA QA Contact: Sergey Kolosov <skolosov>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: ashankar, codonell, fweimer, jeharris, mnewsome, pfrankli, skolosov
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: glibc-2.17-187.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 18:09:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1413146    

Description Jeremy Harris 2016-10-22 22:04:50 UTC 
Description of problem:

 The kernel supports TCP_FASTOPEN (the system include files have it, the
/proc/sys/net/ipv4/tcp_fastopen magic file exists) but there is no definition
of MSG_FASTOPEN (required for applications using the feature to build).

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

How reproducible:
 100%


Additional info:
 F24, with glibc-headers-2.23.1  has it present in /usr/include/bits/socket.h
Comment 3 Jeremy Harris 2016-10-24 10:09:47 UTC 
I was attempting to compile a (bleeding-edge development version) of an
application which can use TCP Fast Open (RFC 7413).  The specific application,
Exim, is not delivered by Red Hat but is the globally dominant internet-facing MTA
according to one scanning site.

TCP Fast Open is also expected to be of interest for general web access
(it can remove one roundtrip time; important for shortlived connections).
Comment 9 errata-xmlrpc 2017-08-01 18:09:25 UTC 
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://access.redhat.com/errata/RHSA-2017:1916