From: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>
To: "Paul Menage" <menage@google.com>
Cc: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
lizf@cn.fujitsu.com, containers@lists.linux-foundation.org
Subject: Re: Question for remount
Date: Sat, 21 Feb 2009 09:45:33 +0900 (JST) [thread overview]
Message-ID: <d7928a87d8c1bf661e3a3b64db9fa988.squirrel@webmail-b.css.fujitsu.com> (raw)
In-Reply-To: <6599ad830902200822u6d453340me718bacac3925040@mail.gmail.com>
Paul Menage さんは書きました：
> On Fri, Feb 20, 2009 at 2:02 AM, KAMEZAWA Hiroyuki
> <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>>
>> 2. /proc/mounts information of release_agent should be updated....
>> when it's overwritten directly.
>
> Yes, definitely. But shouldn't that happen already?
> cgroup_show_options() reports the current value of
> root->release_agent_path in /proc/mounts. Is it possible that mount is
> actually storing/retrieving this information in /etc/mtab, which
> doesn't get updated?
>
Ah, you're right. /proc/mounts is updated but /etc/mtab is not updated.
Hmm..from man mount(1), /etc/mtab is not synchronized with /proc/mounts.
Do we need to allow release_agent override at remount ?
-Kame
next prev parent reply other threads:[~2009-02-21 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 10:02 KAMEZAWA Hiroyuki
2009-02-20 16:22 ` Paul Menage
2009-02-21 0:45 ` KAMEZAWA Hiroyuki [this message]
2009-02-23 2:32 ` Li Zefan
2009-02-23 23:57 ` KAMEZAWA Hiroyuki
2009-02-24 1:33 ` Li Zefan
2009-02-23 2:27 ` Li Zefan
2009-02-23 2:56 ` Li Zefan
2009-02-24 1:36 ` KAMEZAWA Hiroyuki
2009-02-24 1:41 ` Li Zefan
2009-02-24 1:47 ` KAMEZAWA Hiroyuki
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=d7928a87d8c1bf661e3a3b64db9fa988.squirrel@webmail-b.css.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.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