linux-ext4 - Re: [REPOST][PATCH][RFC] vfs: add message print mechanism for the mount/umount into the VFS layer

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20100115173150.f64d6577.toshi.okajima@jp.fujitsu.com>
Date:	Fri, 15 Jan 2010 17:31:50 +0900
From:	Toshiyuki Okajima <toshi.okajima@...fujitsu.com>
To:	Andreas Dilger <adilger@....com>
Cc:	Dave Chinner <david@...morbit.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	"Theodore Ts'o" <tytso@....edu>, linux-fsdevel@...r.kernel.org,
	"linux-ext4@...r.kernel.org development" <linux-ext4@...r.kernel.org>,
	"James C. Browne" <browne@...utexas.edu>
Subject: Re: [REPOST][PATCH][RFC] vfs: add message print mechanism for the
 mount/umount into the VFS layer

On Thu, 14 Jan 2010 23:36:25 -0500
Andreas Dilger <adilger@....com> wrote:

> However, it is doesn't make sense to me to suggest that people add random
> binary status messages to netlink at random times without any kind of
> planning or coordination, since it will just result in a mishmash of
> ad-hoc messages, tools, etc, that will be far worse than what we have
> today instead of improving what exists in /var/log/messages today.

My true purpose is to confirm time when a certain ext3 filesystem
was unmounted.
(We can confirm time when a certain ext3 filesystem was mounted because
ext3 filesystem prints the specific messages at mount. Therefore, to add "unmount"
message into ext3 satisfies my purpose. But to add the one into VFS layer is more
appropriate because we can distinguish the events (mount/unmount) for other
filesystems.)
-------------------------------------------------------------------------------------
Background:
I am an investigator of the root causes of my user incidents. When I investigated
a user's incident, I wanted to know whether a certain mounted ext3 filesystem
had been clearly unmounted or not. Because a certain problem could not occur if its
filesystem had been already unmounted. But now, there is no way to know whether
filesystems were unmounted after the event was done.
Owing to this reason, I want some mechanisms to know whether a certain filesystem
is clearly unmounted after such events was done.
Therefore, I proposed the additional print mechanism in VFS layer.
-------------------------------------------------------------------------------------
For such a purpose, I think the text message in /var/log/messages is more appropriate.

Regards,
Toshiyuki Okajima
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html