From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 529A9C55ABD for ; Tue, 10 Nov 2020 14:14:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0A31E20825 for ; Tue, 10 Nov 2020 14:14:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730666AbgKJOOm (ORCPT ); Tue, 10 Nov 2020 09:14:42 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:38944 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726721AbgKJOOm (ORCPT ); Tue, 10 Nov 2020 09:14:42 -0500 Received: from callcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0AAEEUTs000834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 Nov 2020 09:14:31 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 5C28D420107; Tue, 10 Nov 2020 09:14:30 -0500 (EST) Date: Tue, 10 Nov 2020 09:14:30 -0500 From: "Theodore Y. Ts'o" To: Michal Suchanek Cc: linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org, Andreas Dilger , "Darrick J. Wong" , Ira Weiny , Jan Kara , linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] Tristate moount option comatibility fixup Message-ID: <20201110141430.GA2951190@mit.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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