public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Paul Menage <menage@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	containers@lists.linux-foundation.org
Subject: Re: Question for remount
Date: Mon, 23 Feb 2009 10:32:46 +0800	[thread overview]
Message-ID: <49A20ACE.7020309@cn.fujitsu.com> (raw)
In-Reply-To: <d7928a87d8c1bf661e3a3b64db9fa988.squirrel@webmail-b.css.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> 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 ?
> 

Since we've allowed this behavior, I think we shouldn't disallow it to
supprise users?


  reply	other threads:[~2009-02-23  2:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 10:02 Question for remount KAMEZAWA Hiroyuki
2009-02-20 16:22 ` Paul Menage
2009-02-21  0:45   ` KAMEZAWA Hiroyuki
2009-02-23  2:32     ` Li Zefan [this message]
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=49A20ACE.7020309@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --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