public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bttv hang problem on 2.6.8
Date: Mon, 25 Oct 2004 22:53:07 +0200	[thread overview]
Message-ID: <20041025205306.GA3127@bytesex> (raw)
In-Reply-To: <20041025160145.GA23760@xi.wantstofly.org>

On Mon, Oct 25, 2004 at 06:01:45PM +0200, Lennert Buytenhek wrote:
> On Mon, Oct 25, 2004 at 05:18:41PM +0200, Gerd Knorr wrote:
> 
> > > When there is a background thread doing VIDIOCSYNC in a loop, issuing
> > > VIDIOCSPICT in the current thread on the same file descriptor causes
> > > it to go into uninterruptable sleep and hang.  This is on kernel 2.6.8
> > > using the bttv driver, and appears easily reproducible.
> > 
> > Don't do that.  bttv serializes ioctls with a lock.  Well, not all of
> > them, but the ones which change the state of the filehandle, and both
> > VIDIOCSYNC + VIDIOCSPICT fall into that group.  You simply can't run
> > them in parallel on the same filehandle.
> 
> OK, even though it worked fine on 2.4 I'll buy that, but it still
> shouldn't result in an unkillable process, should it?

Does it?  That wasn't clear.  One of the two threads (the one waiting
for the lock, probably the one doing VIDIOCSPICT) might be unkillable.
Try killing the other thread as well, that should work.  If it doesn't
I'd like to get stack traces for the deadlock case (sysrq-t).

  Gerd

-- 
#define printk(args...) fprintf(stderr, ## args)

      reply	other threads:[~2004-10-25 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25 15:03 bttv hang problem on 2.6.8 Lennert Buytenhek
2004-10-25 15:18 ` Gerd Knorr
2004-10-25 16:01   ` Lennert Buytenhek
2004-10-25 20:53     ` Gerd Knorr [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=20041025205306.GA3127@bytesex \
    --to=kraxel@bytesex.org \
    --cc=buytenh@wantstofly.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