All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : RTDM+POSIX: Avoid leaking binding objects on errors
Date: Mon, 01 Mar 2010 17:19:13 +0100	[thread overview]
Message-ID: <4B8BE901.8050009@domain.hid> (raw)
In-Reply-To: <4B8BD4D4.2060109@domain.hid>

Jan Kiszka wrote:
> Right, the trick is likely to properly maintain the output fds of
> bind_all in that not only pending fds are set, but others are cleared -
> avoids the third bitmap. Still playing with such an approach.

What we are trying to do, in a nutshell, is to create a notion of
stateless binding between a file descriptor and an xnselector. If we
really want to do this, we will have to extend the xnselect interface.
But this looks really wrong to me.

It seems possible to keep the bindings around as long as the file
descriptor exists. The binding is here for this reason, to express the
link between the file descriptor and the thread which runs select, and
its lifecycle should be the same as the file descriptor. And if you want
to signal that such a file descriptor is ready for reading/writing, even
if it is closed, you should be using xnselect_signal. The interface is
there, it is meant for that.

So, the more I think about it, the more I think that we are going in the
wrong direction.

-- 
					    Gilles.


  parent reply	other threads:[~2010-03-01 16:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Nl4tX-0001N9-Hb@domain.hid>
2010-02-26 19:18 ` [Xenomai-core] [Xenomai-git] Jan Kiszka : RTDM+POSIX: Avoid leaking binding objects on errors Gilles Chanteperdrix
2010-02-26 19:25   ` Jan Kiszka
2010-02-27 11:37     ` Jan Kiszka
2010-03-01  8:05       ` Jan Kiszka
2010-03-01  9:11         ` Gilles Chanteperdrix
2010-03-01 10:29           ` Jan Kiszka
2010-03-01 10:37             ` Gilles Chanteperdrix
2010-03-01 11:22               ` Jan Kiszka
2010-03-01 12:46                 ` Jan Kiszka
2010-03-01 12:49                   ` Jan Kiszka
2010-03-01 13:34                 ` Gilles Chanteperdrix
2010-03-01 13:50                   ` Jan Kiszka
2010-03-01 14:15                     ` Gilles Chanteperdrix
2010-03-01 14:22                       ` Jan Kiszka
2010-03-01 14:26                         ` Gilles Chanteperdrix
2010-03-01 14:29                         ` Gilles Chanteperdrix
2010-03-01 14:53                           ` Jan Kiszka
2010-03-01 15:27                             ` Gilles Chanteperdrix
2010-03-01 15:34                             ` Gilles Chanteperdrix
2010-03-01 16:25                               ` Jan Kiszka
2010-03-01 16:19                             ` Gilles Chanteperdrix [this message]
2010-03-01 13:36                 ` Gilles Chanteperdrix

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=4B8BE901.8050009@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Xenomai-core@domain.hid \
    --cc=jan.kiszka@domain.hid \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.