From: Andrew Morton <akpm@osdl.org>
To: mru@kth.se (Måns Rullgård)
Cc: linux-kernel@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: kernel threads holding /dev/console
Date: Sun, 14 Mar 2004 15:03:46 -0800 [thread overview]
Message-ID: <20040314150346.387b59a6.akpm@osdl.org> (raw)
In-Reply-To: <yw1x8yi3dpz8.fsf@ford.guide>
mru@kth.se (Måns Rullgård) wrote:
>
> I'm trying to set up a pivot_root hack to do some things, switch root,
> and then unmount the original root. However, the unmount fails
> because ksoftirqd/0, events/0, kblockd/0 and aio/0 have /dev/console
> opened. Why are they doing this? Can it be prevented? This happens
> when using kernel 2.6.3 (2.6.4 is reportedly broken on Alpha). It
> works with a 2.4 kernel using the same script. Does anyone have a
> hint?
That's a bug.
keventd and friends are currently holding /dev/console open three times.
It's all inherited from init.
Steal the relevant parts of daemonize() to fix that up.
---
25-akpm/kernel/kthread.c | 18 ++++++++++++++++++
1 files changed, 18 insertions(+)
diff -puN kernel/kthread.c~kthread-keeps-files-open kernel/kthread.c
--- 25/kernel/kthread.c~kthread-keeps-files-open 2004-03-14 14:49:21.679226616 -0800
+++ 25-akpm/kernel/kthread.c 2004-03-14 14:57:18.425750128 -0800
@@ -10,6 +10,7 @@
#include <linux/completion.h>
#include <linux/err.h>
#include <linux/unistd.h>
+#include <linux/file.h>
#include <asm/semaphore.h>
struct kthread_create_info
@@ -41,6 +42,21 @@ int kthread_should_stop(void)
return (kthread_stop_info.k == current);
}
+
+static void kthread_exit_files(void)
+{
+ struct fs_struct *fs;
+ struct task_struct *tsk = current;
+
+ exit_fs(tsk); /* current->fs->count--; */
+ fs = init_task.fs;
+ tsk->fs = fs;
+ atomic_inc(&fs->count);
+ exit_files(tsk);
+ current->files = init_task.files;
+ atomic_inc(&tsk->files->count);
+}
+
static int kthread(void *_create)
{
struct kthread_create_info *create = _create;
@@ -50,6 +66,8 @@ static int kthread(void *_create)
int ret = -EINTR;
cpumask_t mask = CPU_MASK_ALL;
+ kthread_exit_files();
+
/* Copy data: it's on keventd's stack */
threadfn = create->threadfn;
data = create->data;
_
next prev parent reply other threads:[~2004-03-14 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 22:27 kernel threads holding /dev/console Måns Rullgård
2004-03-14 23:03 ` Andrew Morton [this message]
2004-03-14 23:15 ` Måns Rullgård
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=20040314150346.387b59a6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
--cc=rusty@rustcorp.com.au \
/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