public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Battersby <tonyb@cybernetics.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] [2.6.29] epoll: fix for epoll_wait sometimes returning events on closed fds
Date: Tue, 24 Feb 2009 15:52:35 -0500	[thread overview]
Message-ID: <49A45E13.80608@cybernetics.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0902241241530.20039@alien.or.mcafeemobile.com>

Davide Libenzi wrote:
> No. Like it has been explained, MT applications can report events for 
> closed files anyway. It is a matter of where the close() happen in time 
> (pretty easy to figure out if you make a time/thread chart).
> As for the other patches, some could be applied, but I didn't look at them 
> deeply and I need time to review them. Will take time to review them 
> tomorrow or the day after.
>
>
>
> - Davide
>
>
>
>   

OK then.  Not the answer I wanted, but that's life.  Good news for
everyone else though - there is no need to remake the patches already in
-mm.  So please ignore the patches marked [2.6.29] and use the patches
marked [-mm] instead (excluding patch #1, which has now been rejected).

Tony


      reply	other threads:[~2009-02-24 20:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 17:26 [PATCH 1/6] [2.6.29] epoll: fix for epoll_wait sometimes returning events on closed fds Tony Battersby
2009-02-24 18:12 ` Eric Dumazet
2009-02-24 18:44   ` Tony Battersby
2009-02-24 19:52     ` Eric Dumazet
2009-02-24 20:36       ` Tony Battersby
2009-02-24 20:45         ` Davide Libenzi
2009-02-24 20:52           ` Tony Battersby [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A45E13.80608@cybernetics.com \
    --to=tonyb@cybernetics.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=dada1@cosmosbay.com \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox