public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Gerd Knorr <kraxel@bytesex.org>, Andrew Morton <akpm@osdl.org>
Subject: [PATCH] saa7134: fix thread shutdown handling
Date: Thu, 21 Jun 2007 14:45:22 -0400	[thread overview]
Message-ID: <467AC742.7070007@suse.com> (raw)

 This patch changes the test for the thread pid from >= 0 to > 0.

 When the saa8134 driver initialization fails after a certain point,
 it goes through the complete shutdown process for the driver. Part
 of shutting it down includes tearing down the thread for tv audio.

 The test for tearing down the thread tests for >= 0. Since the dev
 structure is kzalloc'd, the test will always be true if we haven't
 tried to start the thread yet. We end up waiting on pid 0 to complete,
 which will never happen, so we lock up.

 This bug was observed in Novell Bugzilla 284718, when request_irq()
 failed.

Signed-off-by: Jeff Mahoney <jeffm@suse.com>

---

 drivers/media/video/saa7134/saa7134-tvaudio.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/media/video/saa7134/saa7134-tvaudio.c	2007-06-12 15:45:16.000000000 -0400
+++ b/drivers/media/video/saa7134/saa7134-tvaudio.c	2007-06-15 14:16:14.000000000 -0400
@@ -1005,7 +1005,7 @@
 int saa7134_tvaudio_fini(struct saa7134_dev *dev)
 {
 	/* shutdown tvaudio thread */
-	if (dev->thread.pid >= 0) {
+	if (dev->thread.pid > 0) {
 		dev->thread.shutdown = 1;
 		wake_up_interruptible(&dev->thread.wq);
 		wait_for_completion(&dev->thread.exit);

-- 
Jeff Mahoney
SUSE Labs

             reply	other threads:[~2007-06-21 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 18:45 Jeff Mahoney [this message]
2007-06-23 16:54 ` [PATCH] saa7134: fix thread shutdown handling Andrew Morton
2007-06-23 18:47   ` Mauro Carvalho Chehab

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=467AC742.7070007@suse.com \
    --to=jeffm@suse.com \
    --cc=akpm@osdl.org \
    --cc=kraxel@bytesex.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