All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
Cc: tytso@mit.edu, sct@redhat.com, adilger@sun.com,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/3][RFC] add a message in mount/remount/umount for ext2/ext3/ext4
Date: Tue, 15 Sep 2009 15:20:44 -0700	[thread overview]
Message-ID: <20090915152044.2e4b941f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090915152039.fdca8936.toshi.okajima@jp.fujitsu.com>

On Tue, 15 Sep 2009 15:20:39 +0900
Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com> 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.
> 

I don't think we want to make random printks a part of the kernel
ABI like this.

I understand that it's practical and easy for people to parse the logs
in a local ad-hoc manner such as this, but...  ugh.

If there's a userspace requirement for notification when filesystems
are mounted and unmounted then fine, let's look at that.  What is the
detailed requirement?  What info do we want to see?  What is an
appropriate way of delivering that info?  kobject_uevent() looks like a
suitable place to start.


That being said, there is perhaps a case to made for being more verbose
when filesystems are mounted and unmounted.  But yes, doing that in the
VFS for all filesystems sounds better.  This might upset people who
have thousands of NFS autmounts though.

  parent reply	other threads:[~2009-09-15 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  6:20 [PATCH 0/3][RFC] add a message in mount/remount/umount for ext2/ext3/ext4 Toshiyuki Okajima
2009-09-15 15:15 ` Eric Sandeen
2009-09-16  4:51   ` Toshiyuki Okajima
2009-09-15 22:20 ` Andrew Morton [this message]
2009-09-16  4:55   ` 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=20090915152044.2e4b941f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=toshi.okajima@jp.fujitsu.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.