All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
	alsa-devel@lists.sourceforge.net
Subject: Re: [BUG] alsa-lib leaves sound device open for child processes
Date: Fri, 07 Feb 2003 17:13:10 +0100	[thread overview]
Message-ID: <s5hk7gc133d.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030207135848.567.qmail@web40611.mail.yahoo.com>

At Fri, 7 Feb 2003 13:58:48 +0000 (GMT),
Chris Rankin wrote:
> 
>  --- Paul Davis <paul@linuxaudiosystems.com> wrote:
> > there's a little detail you're forgetting. unless
> > the hw supports multi-open and the current number of
> > subunits is below the limit of the number of opens,
> > then having the descriptor will cause all other
> > attempts to access the device to block (unless they
> > explicitly request non-blocking open, which means
> > they then have to unset that flag for normal
> > application operation
> 
> I hadn't forgotten. The situation to which you are
> referring is called "a bug in the *application*".
> Determining the destinies of resources, delivery of
> signals etc when spawning child processes is the
> application-programmer's responsibility.
> 
> And yes, I have tracked down bugs like this before.
> And I *did* fix the application.

i don't think it's a bug of the alsa-lib, too.
it's a bug of mplayer.  mplayer should be fixed.  period.

but, the problem is that this kind of bugs can be rarely found (nor
appear).  on the contrary, if FD_CLOEXEC is set, you'll be able to
notice what's wrong.  that's what i mentioned "safer".


Takashi


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

  parent reply	other threads:[~2003-02-07 16:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030205205905.7800db0c.sebastian_kapfer@web.de>
2003-02-05 22:39 ` [BUG] alsa-lib leaves sound device open for child processes Chris Rankin
2003-02-06 14:40   ` Sebastian Kapfer
2003-02-06 23:10     ` Chris Rankin
2003-02-07 13:03       ` Paul Davis
2003-02-07 13:58         ` Chris Rankin
2003-02-07 15:22           ` Paul Davis
2003-02-07 16:13           ` Takashi Iwai [this message]
2003-02-07 19:54             ` Chris Rankin
2003-02-07 14:37       ` Sebastian Kapfer
2003-02-07 19:46         ` Chris Rankin
2003-02-08 11:50           ` Jaroslav Kysela
2003-02-08 13:55             ` Sebastian Kapfer
2003-02-08 19:45             ` Sebastian Kapfer
2003-02-08 19:53               ` Jaroslav Kysela
2003-02-12 11:54                 ` Takashi Iwai
2003-02-12 12:46                   ` Jaroslav Kysela
2003-02-07 19:35 Chris Rankin
  -- strict thread matches above, loose matches on Subject: below --
2003-02-05 18:50 Chris Rankin
2003-02-03 22:16 Sebastian Kapfer
2003-02-05 11:20 ` Jaroslav Kysela
2003-02-05 12:42   ` Takashi Iwai
2003-02-05 13:05     ` Jaroslav Kysela
2003-02-05 13:55       ` Takashi Iwai
2003-02-05 14:03         ` Chris Rankin
2003-02-05 14:16           ` Paul Davis

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=s5hk7gc133d.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=paul@linuxaudiosystems.com \
    --cc=rankincj@yahoo.com \
    /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.