Thanks, John. That's almost exactly the approach we were considering.
- Ryan Q
From: John Baldwin
Sent: Friday, February 27, 2015 10:20 AM
To: freebsd-net@freebsd.org
Cc: Quattlebaum, Ryan; Adrian Chadd
Subject: Re: Accessing socket APIs soon after a
2015 1:39 PM
To: Quattlebaum, Ryan
Cc: freebsd-net@freebsd.org
Subject: Re: Accessing socket APIs soon after accept
Oh, I've no idea about -8. If that's what the code does then yeah,
that seems wrong. Is it like that in -10 or -11 ?
-adrian
On 16 January 2015 at 09:07, Quattlebaum, Ryan
wr
syncache code isn't done
configuring?
- Ryan Quattlebaum
From: adrian.ch...@gmail.com on behalf of Adrian Chadd
Sent: Thursday, January 15, 2015 1:20 PM
To: Quattlebaum, Ryan
Cc: freebsd-net@freebsd.org
Subject: Re: Accessing socket APIs soon after accep
Is there anything preventing applications from calling functions e.g.
getsockname() right after accept()? Or is there a recommended pattern that
applications should use to ensure they get correct data? We recently upgraded
to a new version of Apache and are seeing uninitialized data coming back
