From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Arjan van de Ven <arjan@infradead.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org, jtk@us.ibm.com,
wtaber@us.ibm.com, pbadari@us.ibm.com, markv@us.ibm.com,
tytso@us.ibm.com, suparna@in.ibm.com
Subject: Re: [PATCH] fs: Restore files_lock and set_fs_root exports
Date: Thu, 13 Jan 2005 10:29:09 -0800 [thread overview]
Message-ID: <20050113182909.GF1269@us.ibm.com> (raw)
In-Reply-To: <20050113175520.GA24349@kroah.com>
On Thu, Jan 13, 2005 at 09:55:20AM -0800, Greg KH wrote:
> On Thu, Jan 13, 2005 at 09:44:28AM -0800, Paul E. McKenney wrote:
> > On Thu, Jan 13, 2005 at 09:07:12AM -0800, Greg KH wrote:
> > > On Wed, Jan 12, 2005 at 06:51:57PM -0800, Paul E. McKenney wrote:
> > > >
> > > > The current hope is that adding (a) shared and asymmetrically shared
> > > > subtrees between namespaces/locations in the same namespace, (b) stackable
> > > > LSM modules, and (c) dynamic recursive union mount would enable Linux
> > > > to provide this in a technically sound manner. [But this is not clear
> > > > to me yet.]
> > >
> > > I don't see how (b) has anything to do with this. Anyone care to
> > > explain that?
> >
> > It would allow tracking the processes that are using a given view,
> > so that state associated with that view could be cleaned up when the
> > last process exits. One case that motivates this approach:
> >
> > 1. one process creates a view (e.g,. "setview" so that
> > "/vob/foo/bar.c" references version 1.2, just as
> > "/views/v1.2/vob/foo/bar.c" would),
> >
> > 2. this process forks off several descendants, then exits, and
> >
> > 3. the descendant processes eventually exit.
> >
> > The underlying filesystem could use stackable LSM modules to track fork()s
> > and exit()s, allowing it to work out when all processes using a given
> > view had terminated.
>
> But why the "stackable" requirement? Why not just use the LSM interface
> and be done with it?
>
> Or do you want to combine this LSM with SELinux or any other LSM
> (root-plug, seclvl, etc.)? If so, that's asking for trouble (see the
> stackable LSM problems that have been posted multiple times here, and on
> the linux-security-modules mailing list.)
I believe that combining with SELinux is indeed one of the motivations.
And, yes, stackable LSM modules are a bit controversial.
But any way of tracking processes retaining a reference to a view would
meet the need.
Thanx, Paul
next prev parent reply other threads:[~2005-01-13 18:37 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 19:05 Paul E. McKenney
2005-01-06 19:13 ` Christoph Hellwig
2005-01-06 20:07 ` Paul E. McKenney
2005-01-06 20:13 ` Christoph Hellwig
2005-01-06 20:35 ` Mike Waychison
2005-01-06 20:59 ` Christoph Hellwig
2005-01-06 21:35 ` Greg KH
2005-01-06 19:14 ` Al Viro
2005-01-06 20:13 ` Paul E. McKenney
2005-01-06 19:20 ` Arjan van de Ven
2005-01-06 20:15 ` Paul E. McKenney
2005-01-06 20:32 ` Al Viro
2005-01-06 21:04 ` Paul E. McKenney
2005-01-06 21:24 ` Al Viro
2005-01-06 23:26 ` Andrew Morton
2005-01-06 23:11 ` Alan Cox
2005-01-07 0:24 ` Linus Torvalds
2005-01-07 0:48 ` Christoph Hellwig
2005-01-07 7:38 ` Arjan van de Ven
2005-01-06 23:41 ` Christoph Hellwig
2005-01-07 0:29 ` Andrew Morton
2005-01-07 0:26 ` Christoph Hellwig
2005-01-07 3:30 ` Mike Waychison
2005-01-07 9:00 ` Ingo Molnar
2005-01-07 9:15 ` Christoph Hellwig
2005-01-07 12:14 ` Antonio Vargas
2005-01-07 22:00 ` Andrew Morton
2005-01-07 22:19 ` Christoph Hellwig
2005-01-07 22:58 ` Andrew Morton
2005-01-08 15:45 ` Alan Cox
2005-01-07 22:49 ` Alan Cox
2005-01-08 0:12 ` Andrew Morton
2005-01-08 2:20 ` Paul E. McKenney
2005-01-07 23:32 ` Adrian Bunk
2005-01-08 13:10 ` Al Viro
2005-01-07 1:34 ` Alan Cox
2005-01-07 3:17 ` Andrew Morton
2005-01-07 8:12 ` Christoph Hellwig
2005-01-06 23:56 ` [PATCH] add feature-removal-schedule.txt documentation Greg KH
2005-01-07 0:23 ` Christoph Hellwig
2005-01-07 0:32 ` Greg KH
2005-01-07 17:02 ` Randy.Dunlap
2005-01-07 17:54 ` Linus Torvalds
2005-01-07 18:11 ` Greg KH
2005-01-11 12:23 ` [PATCH] cpufreq 2.4 interface removal schedule [Was: Re: [PATCH] add feature-removal-schedule.txt documentation] Dominik Brodowski
2005-01-12 18:41 ` Greg KH
2005-01-07 23:58 ` [PATCH] add feature-removal-schedule.txt documentation Dominik Brodowski
2005-01-12 18:41 ` Greg KH
2005-01-08 18:32 ` Paul E. McKenney
2005-01-08 21:46 ` Alan Cox
2005-01-08 23:03 ` Arjan van de Ven
2005-01-09 6:23 ` Paul E. McKenney
2005-01-09 6:27 ` Paul E. McKenney
2005-01-07 2:02 ` [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-07 1:01 ` Paul E. McKenney
2005-01-07 1:20 ` Al Viro
2005-01-13 2:51 ` Paul E. McKenney
2005-01-13 7:35 ` Arjan van de Ven
2005-01-13 17:53 ` Paul E. McKenney
2005-01-13 17:07 ` Greg KH
2005-01-13 17:44 ` Paul E. McKenney
2005-01-13 17:55 ` Greg KH
2005-01-13 18:29 ` Paul E. McKenney [this message]
2005-01-07 7:33 ` Arjan van de Ven
2005-01-07 8:15 ` Christoph Hellwig
2005-01-07 15:12 ` Paul E. McKenney
2005-01-07 15:23 ` Arjan van de Ven
2005-01-07 15:34 ` Paul E. McKenney
2005-01-07 15:56 ` Arjan van de Ven
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=20050113182909.GF1269@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=jtk@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markv@us.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=suparna@in.ibm.com \
--cc=tytso@us.ibm.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=wtaber@us.ibm.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
Powered by JetHome