linux-ext4 - Re: [PATCH 0/3][RFC] add a message in mount/remount/umount for ext2/ext3/ext4

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: <20090916135153.9b49c58b.toshi.okajima@jp.fujitsu.com>
Date:	Wed, 16 Sep 2009 13:51:53 +0900
From:	Toshiyuki Okajima <toshi.okajima@...fujitsu.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	tytso@....edu, akpm@...ux-foundation.org, adilger@....com,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0/3][RFC] add a message in mount/remount/umount for
 ext2/ext3/ext4

Hi Eric,
Thanks for your comment.

On Tue, 15 Sep 2009 10:15:58 -0500
Eric Sandeen <sandeen@...hat.com> wrote:
> Toshiyuki Okajima wrote:
> > Hi Ted, Andrew and all.
> > 
> > Under the current implementation, we cannot know in the system log 
> > (/var/log/messages) when the filesystem (ext2/ext3/ext4) is unmounted.
> > For enterprise users, they often want to observe certain filesystems'
> > actions (mount/unmount) in the system log. Besides, by the system log, 
> > we occasionally wants to know whether a certain filesystem has been
> > unmounted or not at the time when a problem happens.
> > 
> > The following patch series implement above demand. 
> > Please apply it.
> 
> If this is really a common requirement, perhaps we should at least
> consider putting it in the vfs, in  vfs_kern_mount(),
> generic_shutdown_super(), and do_remount_sb().
Yes. I also thought it was appropriate that where this feature was implemented
was on VFS. But ext3/ext4 has already included the message mechanism which
operates when ext3/ext4 is mounted/remounted.

So, to achieve this feature easily, I have rearranged the message mechanism in
ext3/ext4 (ext2 is newly implemented).

> 
> That way we'll have common behavior and less replicated code; nothing in
> this patch series is unique to ext[234] as far as I can tell.
> 
> sb->s_type->name could be used to print the fs type in a generic message.

Thanks,
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