linux-kernel - Re: [PATCH 2.6.23-rc6 Resending] NETWORKING : Edge Triggered EPOLLOUT events get missed for TCP sockets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <331107.71046.qm@web53704.mail.re2.yahoo.com>
Date:	Wed, 19 Sep 2007 16:50:17 -0700 (PDT)
From:	Nagendra Tomar <tomer_iisc@...oo.com>
To:	Davide Libenzi <davidel@...ilserver.org>,
	David Miller <davem@...emloft.net>
Cc:	tomer_iisc@...oo.com, netdev@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2.6.23-rc6 Resending] NETWORKING : Edge Triggered EPOLLOUT events get missed for TCP sockets


--- Davide Libenzi <davidel@...ilserver.org> wrote:

> On Wed, 19 Sep 2007, David Miller wrote:
> 
> > From: Nagendra Tomar <tomer_iisc@...oo.com>
> > Date: Wed, 19 Sep 2007 15:37:09 -0700 (PDT)
> > 
> > > With the SOCK_NOSPACE check in tcp_check_space(), this epoll_wait call will 
> > > not return, even when the incoming acks free the buffers.
> > >         Note that this patch assumes that the SOCK_NOSPACE check in
> > > tcp_check_space is a trivial optimization which can be safely removed.
> > 
> > I already replied to your patch posting explaining that whatever is
> > not setting SOCK_NOSPACE should be fixed instead.
> > 
> > Please address that, thanks.
> 
> You're not planning of putting the notion of a SOCK_NOSPACE bit inside a 
> completely device-unaware interface like epoll, I hope?
> 

Definitely not ! 

The point is that the "tcp write space available" 
wakeup does not get called if SOCK_NOSPACE bit is not set. This was
fine when the wakeup was merely a wakeup (since SOCK_NOSPACE bit 
indicated that someone really cared abt the wakeup). Now after the
introduction of callback'ed wakeups, we might have some work to
do inside the callback even if there is nobody interested in the wakeup
at that point of time. 

In this particular case the ep_poll_callback is not getting called and
hence the socket fd is not getting added to the ready list.

Thanx,
Tomar




      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
-
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/