Re: pipe write buffer
- From: davids@xxxxxxxxxxxxx
- Date: 21 Jul 2006 18:21:56 -0700
Rainer Temme wrote:
davids@xxxxxxxxxxxxx wrote:
So, either a packet is discarded (in this case POLLIN is not signalled)
or POLLIN is signalled and there is something to read, or an
error-condition.
You are incorrect. Linux in fact does that and it in fact broke code.
David,
please show us/me sume code that shows this behaviour.
Rainer
See the Linux inetd denial of service attack thread. Unfortunately,
inetd assumed that a read hit for 'select' guaranteed that a
subseqeuent 'read' would not block. However, the Linux kernel decided
to drop the packet in-between the 'select' hit and the 'read' hit
(which it has the absolute right to do at any time), and 'inetd'
blocked in 'read'.
DS
.
- Follow-Ups:
- Re: pipe write buffer
- From: Rainer Temme
- Re: pipe write buffer
- References:
- pipe write buffer
- From: smiffy
- Re: pipe write buffer
- From: Rainer Temme
- Re: pipe write buffer
- From: Barry Margolin
- Re: pipe write buffer
- From: Rainer Temme
- Re: pipe write buffer
- From: davids
- Re: pipe write buffer
- From: Rainer Temme
- Re: pipe write buffer
- From: davids
- Re: pipe write buffer
- From: Rainer Temme
- Re: pipe write buffer
- From: davids
- Re: pipe write buffer
- From: Rainer Temme
- pipe write buffer
- Prev by Date: Re: What blocks a write to a socket pair?
- Next by Date: Re: What blocks a write to a socket pair?
- Previous by thread: Re: pipe write buffer
- Next by thread: Re: pipe write buffer
- Index(es):
Relevant Pages
|
