* socket state after accept() return
@ 2013-01-18 21:42 horseriver
2013-01-19 15:50 ` Mulyadi Santosa
0 siblings, 1 reply; 2+ messages in thread
From: horseriver @ 2013-01-18 21:42 UTC (permalink / raw)
To: kernelnewbies
hi:
For one socket , which has been returned by accept() call , does its sk_state
is assuredly already TCPF_ESTABLISHED ?
thanks!
^ permalink raw reply [flat|nested] 2+ messages in thread
* socket state after accept() return
2013-01-18 21:42 socket state after accept() return horseriver
@ 2013-01-19 15:50 ` Mulyadi Santosa
0 siblings, 0 replies; 2+ messages in thread
From: Mulyadi Santosa @ 2013-01-19 15:50 UTC (permalink / raw)
To: kernelnewbies
On Sat, Jan 19, 2013 at 4:42 AM, horseriver <horserivers@gmail.com> wrote:
> hi:
>
> For one socket , which has been returned by accept() call , does its sk_state
> is assuredly already TCPF_ESTABLISHED ?
the context is TCP, right?
if so, then yes (this is without deep check in linux network stack
code, just based on general logic)
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-01-19 15:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-18 21:42 socket state after accept() return horseriver
2013-01-19 15:50 ` Mulyadi Santosa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).