From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Michal Suchanek <msuchanek@suse.de>
Cc: linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
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: Re: [PATCH 0/2] Tristate moount option comatibility fixup
Date: Tue, 10 Nov 2020 09:14:30 -0500 [thread overview]
Message-ID: <20201110141430.GA2951190@mit.edu> (raw)
In-Reply-To: <cover.1604948373.git.msuchanek@suse.de>
On Mon, Nov 09, 2020 at 08:10:07PM +0100, Michal Suchanek wrote:
> 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.
Which applications? Name them.
We *really* don't want to encourage applications to make decisions
only based on the mount options. For example, it could be that the
application's files will have the S_DAX flag set.
It would be a real shame if we are actively encourage applications to
use a broken configuration mechanism which was only used as a hack
while DAX was in experimental status.
- Ted
next prev parent reply other threads:[~2020-11-10 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 19:10 [PATCH 0/2] Tristate moount option comatibility fixup Michal Suchanek
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 ` Theodore Y. Ts'o [this message]
2020-11-10 18:35 ` [PATCH 0/2] Tristate moount option comatibility fixup 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=20201110141430.GA2951190@mit.edu \
--to=tytso@mit.edu \
--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=msuchanek@suse.de \
/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.