From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix ext4_show_options to show the correct mount options.
Date: Wed, 24 Oct 2007 23:48:15 +0530 [thread overview]
Message-ID: <471F8C67.2020907@linux.vnet.ibm.com> (raw)
In-Reply-To: <471F8705.9090308@redhat.com>
Eric Sandeen wrote:
> Aneesh Kumar K.V wrote:
>> We need to look at the default value and make sure
>> the mount options are not set via default value
>> before showing them via ext4_show_options
>
> Hm, does this jive with the comment about what's intended?
>
> /*
> * Show an option if
> * - it's set to a non-default value OR
> * - if the per-sb default is different from the global default
> */
>
> Aren't you now omitting the option if it's set in the per-sb default?
>
> For example the "debug" option; it's off by default, globally. The
> above comment suggests that if you have overridden that global default
> in the per-sb "default mount options" then it should be shown; this sort
> of makes sense to me because tune2fs calls these "default mount
> options," I'd expect them to behave exactly as if you had explicitly
> mounted with them.
>
> With your patch, if you've set debug as default, it no longer shows up,
> right?
I was looking at commit 93d44cb275f3eba720617a8c5b00d51a8e0e9049
Using mtab is problematic for various reasons, one of them is that
unprivileged mounts won't turn up in there. So we want to get rid of it, and
use /proc/mounts instead.
But most filesystems are lazy, and are not showing all mount options. Which
means, that without mtab, the user won't be able to see some or all of the
options.
It would be nice if the generic code could remember the mount options, and
show them without the need to add extra code to filesystems. But this is not
easy, because different filesystems handle mount options given options, and
not tough the rest. This is not taken into account by mount(8) either, so
/etc/mtab will be broken in this case.
So my understanding was that we are supposed to make /proc/mounts show the same output as
/etc/mtab did. In that case should we be showing the the default set in super block ?
-aneesh
next prev parent reply other threads:[~2007-10-24 18:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:47 Patches for review Aneesh Kumar K.V
2007-10-24 16:47 ` Aneesh Kumar K.V
2007-10-24 16:47 ` Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Change the default behaviour on error Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Fix mballoc BUG when running compilebench Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Enable delalloc and mballoc by default Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Show mballoc and delalloc options Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Fix ext4_show_options to show the correct mount options Aneesh Kumar K.V
2007-10-24 17:55 ` Eric Sandeen
2007-10-24 18:18 ` Aneesh Kumar K.V [this message]
2007-10-24 18:25 ` Eric Sandeen
2007-10-24 17:24 ` [PATCH] ext4: Show mballoc and delalloc options Eric Sandeen
2007-10-24 17:22 ` [PATCH] ext4: Enable delalloc and mballoc by default Eric Sandeen
2007-10-24 17:30 ` Aneesh Kumar K.V
2007-10-24 19:15 ` Mingming Cao
2007-10-24 21:06 ` Andreas Dilger
2007-10-24 21:15 ` Eric Sandeen
2007-10-24 22:59 ` Andreas Dilger
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=471F8C67.2020907@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).