linux-kernel - Re: Question for remount

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6599ad830902200822u6d453340me718bacac3925040@mail.gmail.com>
Date:	Fri, 20 Feb 2009 08:22:45 -0800
From:	Paul Menage <menage@...gle.com>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	lizf@...fujitsu.com, containers@...ts.linux-foundation.org
Subject: Re: Question for remount

On Fri, Feb 20, 2009 at 2:02 AM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@...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?

Paul
--
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/