All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: question on pivot_root and kernel threads
Date: Tue, 10 Feb 2004 11:49:16 -0500	[thread overview]
Message-ID: <40290B8C.5000208@nortelnetworks.com> (raw)


I've got an embedded system that we're trying to move from 2.4.18 to 
2.4.22 (which involves a userspace upgrade as well).  It netboots with 
an initrd, and then at startup converts it to a tmpfs, unmounts the 
original ramdisk, and frees the memory.

With 2.4.22 suddenly it started complaining about being unable to 
unmount the original ramdisk.  After some digging, it seems that the 
kernel threads (keventd, ksoftirqd_CPU0, kswapd, bdflush, kupdated, and 
mtdblockd) are starting up with stdin/stdout/stderr set to /dev/console 
in the original ramdisk.  When I do the pivot_root so that the original 
ramdisk is mounted at "/mnt", I end up with a bunch of references to 
"/mnt/dev/console", and I can't unmount "/mnt" since the refcount is 
nonzero.

At a guess, its related to this thread:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=hpYn.1fz.21%40gated-at.bofh.it

Did this ever get resolved properly?


Thanks,

Chris


-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

                 reply	other threads:[~2004-02-10 16:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40290B8C.5000208@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.