From: Michal Suchanek <msuchanek@suse.de>
To: linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org
Cc: Michal Suchanek <msuchanek@suse.de>,
"Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Ira Weiny <ira.weiny@intel.com>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Tristate moount option comatibility fixup
Date: Mon, 9 Nov 2020 20:10:07 +0100 [thread overview]
Message-ID: <cover.1604948373.git.msuchanek@suse.de> (raw)
Hello,
after the tristate dax option change some applications fail to detect
pmem devices because the dax option no longer shows in mtab when device
is mounted with -o dax.
At first it might seem stupid to detect pmem by looking at the mount
options.
However, if the application actually wants a mount point properly
configured for dax rather than just backed by pmem I do not see any
other easy way.
Also this happens during early installtion steps when the mounted
filesystem is typically empty and you want to perform non-destructive
detection.
If there are better ways to detect dax enabled mount poins I want to
hear all about it. In the meantime we have legacy applications to
support.
It also makes sense that when you mount a device with -o dax it actually
shows dax in the mount options. Not doind so is confusing for humans as
well.
Thanks
Michal
Michal Suchanek (2):
xfs: show the dax option in mount options.
ext4: show the dax option in mount options
References: bsc#1178366
fs/ext4/super.c | 2 +-
fs/xfs/xfs_super.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-11-09 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 19:10 Michal Suchanek [this message]
2020-11-09 19:10 ` [PATCH 1/2] xfs: show the dax option in mount options Michal Suchanek
2020-11-09 19:24 ` Eric Sandeen
2020-11-09 19:24 ` Darrick J. Wong
2020-11-09 20:27 ` Michal Suchánek
2020-11-09 21:08 ` Dave Chinner
2020-11-11 10:28 ` Michal Suchánek
2020-11-12 1:49 ` Dave Chinner
2020-11-12 11:12 ` Michal Suchánek
2020-11-12 15:10 ` Jan Kara
2020-11-12 16:08 ` Ira Weiny
2020-12-01 16:29 ` Michal Suchánek
2020-11-10 18:38 ` Christoph Hellwig
2020-11-09 19:10 ` [PATCH 2/2] ext4: " Michal Suchanek
2020-11-10 14:14 ` [PATCH 0/2] Tristate moount option comatibility fixup Theodore Y. Ts'o
2020-11-10 18:35 ` Christoph Hellwig
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=cover.1604948373.git.msuchanek@suse.de \
--to=msuchanek@suse.de \
--cc=adilger.kernel@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=ira.weiny@intel.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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 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).