Accessing socket APIs soon after accept

[Adrian Chadd]

On 15 January 2015 at 08:29, Quattlebaum, Ryan
<Ryan.Quattlebaum at netapp.com> wrote:
> 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 from a few of these calls.

I'm under the impression that once you get the FD from accept(), it
should be fully formed and ready.

Which version of FreeBSD/apache is it? can you come up with a test
case that shows that it's happening?



-adrian

> Thanks,
>
> Ryan Quattlebaum
> Software Developer, NetApp, Inc.
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"