From: Theodore Tso <tytso@mit.edu>
To: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
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: Wed, 30 Sep 2009 23:55:44 -0400 [thread overview]
Message-ID: <20091001035544.GT24383@mit.edu> (raw)
In-Reply-To: <4AC41FF1.7060703@jp.fujitsu.com>
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.
- Ted
next prev parent reply other threads:[~2009-10-01 3:55 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 [this message]
2009-10-01 4:32 ` Toshiyuki Okajima
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=20091001035544.GT24383@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=toshi.okajima@jp.fujitsu.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 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.