Date: Thu, 15 Jan 2015 10:20:06 -0800 From: Adrian Chadd <adrian@freebsd.org> To: "Quattlebaum, Ryan" <Ryan.Quattlebaum@netapp.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Accessing socket APIs soon after accept Message-ID: <CAJ-VmonYaAUior3aGBioVUvMPM1OMHJnHt7-rQgzMGQ4co4ATQ@mail.gmail.com> In-Reply-To: <1421339375968.94209@netapp.com> References: <1421339375968.94209@netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 January 2015 at 08:29, Quattlebaum, Ryan <Ryan.Quattlebaum@netapp.com> wrote: > Is there anything preventing applications from calling functions e.g. get= sockname() right after accept()? Or is there a recommended pattern that app= lications should use to ensure they get correct data? We recently upgraded = to a new version of Apache and are seeing uninitialized data coming back fr= om 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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonYaAUior3aGBioVUvMPM1OMHJnHt7-rQgzMGQ4co4ATQ>