From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Zhang Yi <yi.zhang@huawei.com>
Cc: <linux-ext4@vger.kernel.org>, <tytso@mit.edu>,
<adilger.kernel@dilger.ca>, <jack@suse.cz>, <yukuai3@huawei.com>,
<yebin10@huawei.com>, <liuzhiqiang26@huawei.com>,
<liangyun2@huawei.com>
Subject: Re: [RFC PATCH] ext4: add unmount filesystem message
Date: Tue, 12 Apr 2022 12:01:37 -0400 [thread overview]
Message-ID: <87pmlmcmu6.fsf@collabora.com> (raw)
In-Reply-To: <20220412145320.2669897-1-yi.zhang@huawei.com> (Zhang Yi's message of "Tue, 12 Apr 2022 22:53:20 +0800")
Zhang Yi <yi.zhang@huawei.com> writes:
> Now that we have kernel message at mount time, system administrator
> could acquire the mount time, device and options easily. But we don't
> have corresponding unmounting message at umount time, so we cannot know
> if someone umount a filesystem easily. Some of the modern filesystems
> (e.g. xfs) have the umounting kernel message, so add one for ext4
> filesystem for convenience.
>
> EXT4-fs (sdb): mounted filesystem with ordered data mode. Quota mode: none.
> EXT4-fs (sdb): unmounting filesystem.
I don't think sysadmins should be relying on the kernel log for this,
since the information can easily be overwritten by new messages there.
Is there a reason why you can't just monitor /proc/self/mountinfo?
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
> ---
> fs/ext4/super.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 81749eaddf4c..bdecf62f4b55 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -1199,6 +1199,9 @@ static void ext4_put_super(struct super_block *sb)
> int aborted = 0;
> int i, err;
>
> + if (___ratelimit(&ext4_mount_msg_ratelimit, "EXT4-fs unmount"))
> + ext4_msg(sb, KERN_INFO, "unmounting filesystem.");
> +
> ext4_unregister_li_request(sb);
> ext4_quota_off_umount(sb);
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2022-04-12 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 14:53 [RFC PATCH] ext4: add unmount filesystem message Zhang Yi
2022-04-12 16:01 ` Gabriel Krisman Bertazi [this message]
2022-04-13 1:35 ` Theodore Ts'o
2022-04-13 2:23 ` Zhang Yi
2022-04-13 3:51 ` Darrick J. Wong
2022-04-13 6:33 ` Zhang Yi
2022-04-13 8:16 ` Jan Kara
2022-04-12 16:40 ` Jan Kara
2022-05-13 21:15 ` Theodore Ts'o
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=87pmlmcmu6.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=liangyun2@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=tytso@mit.edu \
--cc=yebin10@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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.