[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120331154625.GA6241@albatros>
Date: Sat, 31 Mar 2012 19:46:25 +0400
From: Vasiliy Kulikov <segoon@...nwall.com>
To: Arkadiusz Miśkiewicz <a.miskiewicz@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Valdis.Kletnieks@...edu,
linux-kernel@...r.kernel.org, Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [PATCH] proc: reset mount options after the last procfs umount
On Sat, Mar 31, 2012 at 17:31 +0200, Arkadiusz Miśkiewicz wrote:
> On Saturday 31 of March 2012, Vasiliy Kulikov wrote:
> > On Sat, Mar 31, 2012 at 16:19 +0200, Arkadiusz Miśkiewicz wrote:
> > > "after all procs are umounted". For me such way is fine but still can
> > > suprise people.
> > >
> > > Anyway - what's the problem with implementing support for separate
> > > options for each mount point?
> >
> > Well, IMHO multiple procs in one pid namespace is a very strange system
> > configuration. I didn't see such installations.
>
> I have one real world case - linux-vserver.org guests where pid namespace is
> optional and usually not used.
I'm a vserver noob. Does it allow using multiple containers sharing the same
pid namespace? Having only a single init process?
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists