mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "BALBIR SINGH" <balbir.singh@wipro.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Hotplug CPU prep III: daemonize idle tasks
Date: Mon, 13 May 2002 12:01:04 +1000	[thread overview]
Message-ID: <E177597-0001TA-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Thu, 09 May 2002 17:36:43 +0530." <AAEGIMDAKGCBHLBAACGBAELNCHAA.balbir.singh@wipro.com>

In message <AAEGIMDAKGCBHLBAACGBAELNCHAA.balbir.singh@wipro.com> you write:
> I tried a version of __daemonize in 2.4. It panics in
> schedule()
> 
>         prepare_to_switch();
>         {
>                 struct mm_struct *mm = next->mm;
>                 struct mm_struct *oldmm = prev->active_mm;
>                 if (!mm) {
>                         if (next->active_mm) BUG();
> 
> I got hit by the BUG() in 2.4, I think prepare_to_switch has
> moved to specific archs in 2.5. A quick look showed that
> this issue no longer exists in 2.5.

Uhhh... there are many other problems if you are trying to do this on
a "live" process.  idle process creation is a special case because it
has never been run yet.

This is not a generic "daemonize this task" mechanism!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2002-05-13  1:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09  8:50 Rusty Russell
2002-05-09 12:06 ` BALBIR SINGH
2002-05-13  2:01   ` Rusty Russell [this message]
2002-05-13  6:19     ` BALBIR SINGH

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=E177597-0001TA-00@wagner.rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=balbir.singh@wipro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 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®