From: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] cgroup: deprecate remount option changes and "name=" mount option
Date: Wed, 14 Mar 2012 21:39:51 -0500 [thread overview]
Message-ID: <4F615677.5080105@canonical.com> (raw)
In-Reply-To: <20120314215228.GI7349-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
On 03/14/2012 04:52 PM, Tejun Heo wrote:
> This patch removes the following features.
>
> * Rebinding subsys by remount: Never reached useful state - only works
> on empty hierarchies.
>
> * release_agent update by remount: release_agent itself will be
> replaced with conventional fsnotify notification.
meaning any applications currently relying on release agent will need to
add a daemon using fsnotify? Or will it be done in the kernel?
thanks,
-serge
next prev parent reply other threads:[~2012-03-15 2:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120314215228.GI7349@google.com>
[not found] ` <20120314215228.GI7349-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-03-14 23:29 ` [PATCH] cgroup: deprecate remount option changes and "name=" mount option Lennart Poettering
2012-03-15 2:39 ` Serge Hallyn [this message]
2012-03-15 16:56 ` [PATCH] cgroup: deprecate remount option changes " Tejun Heo
[not found] ` <20120315165655.GD32137-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-03-15 19:36 ` Lennart Poettering
[not found] ` <20120315193635.GD32661-kS5D54t9nk0aINubkmmoJbNAH6kLmebB@public.gmane.org>
2012-03-15 19:45 ` Tejun Heo
2012-03-31 16:41 ` Tejun Heo
[not found] ` <20120314232925.GA16973@tango.0pointer.de>
[not found] ` <20120314232925.GA16973-kS5D54t9nk0aINubkmmoJbNAH6kLmebB@public.gmane.org>
2012-03-15 16:54 ` [PATCH] cgroup: deprecate remount option changes and "name=" " Tejun Heo
[not found] ` <20120315165402.GC32137@google.com>
[not found] ` <20120315165402.GC32137-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-03-15 19:33 ` Lennart Poettering
2012-03-14 21:52 Tejun Heo
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=4F615677.5080105@canonical.com \
--to=serge.hallyn-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox