All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Yek <dyek@real.com>
To: "Rémi Denis-Courmont" <rem@videolan.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: How to close ALSA device nodes? / ALSA's fds
Date: Fri, 23 Oct 2009 11:51:45 -0700	[thread overview]
Message-ID: <4AE1FB41.2020408@real.com> (raw)
In-Reply-To: <200910182038.34252.rem@videolan.org>

[Branch the thread for a separate suggestion...]

Rémi Denis-Courmont wrote:
> Le dimanche 18 octobre 2009 20:13:15 Robert Hancock, vous avez écrit :
>>> From the earlier thread, I reckon that ALSA developers consider that
>>> this
>>> is an upper-layer issue. Maybe so, but then how is the upper-layer
>>> supposed to find which file descriptors ALSA-lib has opened - if any?
>>> Conversely, if ALSA- lib won't tell while file descriptors it is using,
>>> what could possibly be the use case for not closing those on exec?
>> I agree that it's a difficult problem for an app that wants to fork
>> and exec another process.. I'd think really should be some way for an
>> app to control the CLOEXEC flag for the file descriptors that alsa-lib
>> has open..
> <snip>
>
> That said, I still fail to see any potential use case to not set the
> flag.
> Since ALSA-lib won't let the application know about the file handles, any
> application cannot a use them across exec() in the first place.

Is snd_pcm_poll_descriptors() adequate for this particular issue?

Regards,

-- 
Daniel Yek.


_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2009-10-23 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 17:38 How to close ALSA device nodes? Rémi Denis-Courmont
2009-10-22 22:55 ` Daniel Yek
2009-10-23  9:49   ` Rémi Denis-Courmont
2009-10-23 16:44     ` Surrogate Parent Model / " Daniel Yek
2009-10-23 18:51 ` Daniel Yek [this message]
2009-10-24 14:37   ` How to close ALSA device nodes? / ALSA's fds Rémi Denis-Courmont

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=4AE1FB41.2020408@real.com \
    --to=dyek@real.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=rem@videolan.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 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.