Hi Folks!
when creating a private namespace (CLONE_NS) and
then mounting an ext3 filesystem, a new kernel
thread (kjournald) is created, which keeps a
reference to the namespace, which after the the
process exits, remains and blocks access to the
block device, as it is still bd_claim-ed.
this leaves a private namespace behind and a
block device which cannot be opened exclusively.
unmount is not an option, as the namespace is
not longer reachable.
this behaviour seems to be there since ever,
well since namespaces and kjournald exists :)
the following 'cruel' hack 'solves' this issue
best,
Herbert
--- fs/jbd/journal.c.orig 2006-01-03 17:29:56 +0100
+++ fs/jbd/journal.c 2006-02-18 02:23:21 +0100
@@ -33,6 +33,7 @@
#include <linux/mm.h>
#include <linux/suspend.h>
#include <linux/pagemap.h>
+#include <linux/namespace.h>
#include <asm/uaccess.h>
#include <asm/page.h>
#include <linux/proc_fs.h>
@@ -116,6 +117,13 @@ static int kjournald(void *arg)
struct timer_list timer;
daemonize("kjournald");
+ {
+ struct namespace *ns = current->namespace;
+
+ current->namespace = NULL;
+ put_namespace(ns);
+ }
+
/* Set up an interval timer which can be used to trigger a
commit wakeup after the commit interval expires */
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
