[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <005501c6db44$102b73a0$294b82ce@stuartm>
Date: Mon, 18 Sep 2006 13:01:20 -0400
From: "Stuart MacDonald" <stuartm@...necttech.com>
To: "'Michael Kerrisk'" <mtk-manpages@....net>,
"'Andi Kleen'" <ak@...e.de>
Cc: <linux-kernel@...r.kernel.org>
Subject: RE: TCP stack behaviour question
From: Michael Kerrisk [mailto:mtk-manpages@....net]
> Von: Andi Kleen <ak@...e.de>
> > On Monday 18 September 2006 16:19, Stuart MacDonald wrote:
> > > From: Andi Kleen [mailto:ak@...e.de]
> > > > > # man 7 ip
> > > > > ..
> > > > > Note that TCP has no error queue;
> MSG_ERRQUEUE is
> > > > > illegal on SOCK_STREAM sockets. Thus all errors are
> returned by
> > > > > socket function return or SO_ERROR only.
> > > > >
> > > > > Maybe the man page is wrong? That's from my FC 3 install.
> > > >
> > > > The sentence is correct, but TCP has a IP_RECVERR that works
> > > > differently without a queue. Basically it doesn't delay
> the error
> > > > reporting for incoming ICMPs to the last retransmit, but reports
> > > > them immediately. This is documented in tcp(7)
> > >
> > > I read that too, but didn't know which one was correct,
> so I erred on
> > > the side of caution and believed ip(7).
> >
> > Ok maybe it's a bit misleading. Michael, you might want to clarify.
>
> Can some one of you propose a better text please?
Perhaps
Note that TCP has no error queue; MSG_ERRQUEUE is illegal on
SOCK_STREAM sockets. IP_RECVERR is valid for TCP, but all errors are
returned by socket function return or SO_ERROR only.
?
..Stu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists