public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Mateusz.Blaszczyk@nask.pl
Cc: axboe@suse.de, linux-kernel@vger.kernel.org,
	Nigel Cunningham <ncunningham@users.sourceforge.net>
Subject: Re: [pktcdvd] Badness in fork.c:91 then Oops
Date: 30 Dec 2004 20:19:19 +0100	[thread overview]
Message-ID: <m3acrvh9vs.fsf@telia.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0412301854420.2875@boromir>

Mateusz.Blaszczyk@nask.pl writes:

> PKTCDVD seems to create some badness in kernel/fork, line 91:
> 
> I loaded pktcdvd manaully end everything was fine
> 
> Dec 30 08:32:46 localhost kernel: pktcdvd: v0.2.0a 2004-07-14 Jens Axboe (axboe@suse.de) and petero2@telia.com
> 
> Then I tried to map cd drive using udftools' pktsetup (v.1.0.3b):
> 
> Dec 30 08:33:27 localhost kernel: cdrom: This disc doesn't have any tracks I recognize!
> Dec 30 08:33:27 localhost kernel: Badness in __put_task_struct at kernel/fork.c:91
...
> Dec 30 08:05:52 localhost kernel: Software Suspend Core.
> Dec 30 08:05:52 localhost kernel: Software Suspend text mode support loaded.
> Dec 30 08:05:52 localhost kernel: Software Suspend LZF Compression Driver registered.
> Dec 30 08:05:52 localhost kernel: Software Suspend Swap Writer registered.

It's actually the swsusp 2 patches that don't handle the pktcdvd
driver correctly. The kthread_run() function was changed, but the
pktcdvd driver wasn't updated accordingly. I think this patch will fix
the problem.

--- linux/drivers/block/pktcdvd.c.old	2004-12-30 20:11:54.400478672 +0100
+++ linux/drivers/block/pktcdvd.c	2004-12-30 20:12:09.617165384 +0100
@@ -2364,7 +2364,7 @@
 	pkt_init_queue(pd);
 
 	atomic_set(&pd->cdrw.pending_bios, 0);
-	pd->cdrw.thread = kthread_run(kcdrwd, pd, "%s", pd->name);
+	pd->cdrw.thread = kthread_run(kcdrwd, pd, PF_SYNCTHREAD, "%s", pd->name);
 	if (IS_ERR(pd->cdrw.thread)) {
 		printk("pktcdvd: can't start kernel thread\n");
 		ret = -ENOMEM;

-- 
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340

  reply	other threads:[~2004-12-30 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 18:00 [pktcdvd] Badness in fork.c:91 then Oops Mateusz.Blaszczyk
2004-12-30 19:19 ` Peter Osterlund [this message]
2005-01-03  7:06   ` Mateusz.Blaszczyk

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=m3acrvh9vs.fsf@telia.com \
    --to=petero2@telia.com \
    --cc=Mateusz.Blaszczyk@nask.pl \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@users.sourceforge.net \
    /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