From: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
To: Theodore Tso <tytso@mit.edu>
Cc: akpm@linux-foundation.org, adilger@sun.com, sandeen@redhat.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/3][RFC](Repost) ext4: add a message in remount/umount for ext4
Date: Thu, 01 Oct 2009 13:32:31 +0900 [thread overview]
Message-ID: <4AC430DF.5040505@jp.fujitsu.com> (raw)
In-Reply-To: <20091001035544.GT24383@mit.edu>
Hi Ted,
thank you for your comment.
Theodore Tso wrote:
> On Thu, Oct 01, 2009 at 12:20:17PM +0900, Toshiyuki Okajima wrote:
>> I am recognizing it. But I think I have already explained its answer as follows:
>> - A print mechanism has already been included at mount time.
>
> It's true that some file systems already are printing a message at
> mount time; but when we abstract up something to the VFS layer, that's
> also an opportunity to remove some kernel printk's from some
> filesystems, including ext2/3/4 at the same time this feature is
> introduced.
>
>>> filesystem specific information, but that could be handled via a new
>>> method function in struct super_ops:
>>>
>>> mount_msg(struct super *sb, char *buf, int buflen)
>>>
>
> Note that what I was assuming is that we would is something like this
> in the VFS mount code:
>
> printk(KERN_INFO "Device %s mounted file system type %s read-%s%s\n",
> sb->s_sid, sb->s_type->name,
> sb->s_flags & MS_RDONLY ? "only" : "write",
> sb->s_op->mount_msg ? sb->s_op->mount_msg(sb) : "");
>
> The advantage of this is that we would now have a single consistent
> kernel message for all file systems, with some room for file system
> specific message.
OK.
I try to implement the message mechanism at mount/umount time like
your description ASAP.
Best Regards,
Toshiyuki Okajima
prev parent reply other threads:[~2009-10-01 4:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 6:49 [PATCH 3/3][RFC](Repost) ext4: add a message in remount/umount for ext4 Toshiyuki Okajima
2009-09-30 17:22 ` Theodore Tso
2009-10-01 3:20 ` Toshiyuki Okajima
2009-10-01 3:55 ` Theodore Tso
2009-10-01 4:32 ` Toshiyuki Okajima [this message]
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=4AC430DF.5040505@jp.fujitsu.com \
--to=toshi.okajima@jp.fujitsu.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.