mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lluís Batlle i Rossell" <viriketo@gmail.com>
To: "Lluís Batlle i Rossell" <viriketo@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fds jumping between processes
Date: Fri, 14 May 2010 11:11:37 +0200	[thread overview]
Message-ID: <20100514091135.GD8773@vicerveza.homeunix.net> (raw)
In-Reply-To: <20100514090903.GC8773@vicerveza.homeunix.net>

Bah, forget it! firefox problem. Sorry for the noise.

On Fri, May 14, 2010 at 11:09:03AM +0200, Lluís Batlle i Rossell wrote:
> Hello,
> here is quite an open bug report... I could not reproduce this again, but it
> involves the fds opened of a killed process being passed to another process, or
> something like this.
> 
> I'm using vanilla 2.6.33.3 in x86_64.
> I was using skype, talking through it using alsa, and trying the
> 'share desktop' feature, it died. Starting it again, it could not open the alsa
> device. Using fuser:
> 
> ...:/dev/snd]$ fuser *
> controlC0:           32341
> pcmC0D0p:            32341
> timer:               32341
> 
> Which that was:
> $ ps ax | grep 323
> 32341 ?        S      0:01 /home/xxx/.nix-profile/bin/xpdf /tmp/xxx.pdf
> 
> So, after skype (using alsa) died, the xpdf process took the soundcard fds
> skype had. It does not make much sense xpdf to use sound... so I guess something
> worth looking happened.
> 
> I don't have more details. Killing xpdf made the new skype open the alsa device
> properly.
> 
> Sorry for not having analised the situation better. Now I cannot reproduce it
> anymore. Maybe this will make someone knowing say "ah, let me look if ...". I
> just thought if this is a bug in the kernel, it can involve security problems.
> 
> Thank you,
> Lluís.

      reply	other threads:[~2010-05-14  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14  9:09 Lluís Batlle i Rossell
2010-05-14  9:11 ` Lluís Batlle i Rossell [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=20100514091135.GD8773@vicerveza.homeunix.net \
    --to=viriketo@gmail.com \
    --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

all inboxes | Powered by JetHome®