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=-8.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable 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 5D3CCC8301F for ; Tue, 1 Dec 2020 16:56:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EF9E72076C for ; Tue, 1 Dec 2020 16:56:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="JGbilGkh" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391673AbgLAQ4A (ORCPT ); Tue, 1 Dec 2020 11:56:00 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:24270 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390732AbgLAQz7 (ORCPT ); Tue, 1 Dec 2020 11:55:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606841673; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=NwanTEN/hmPAe2sJLS/eqUBj8LvT15GIF6AmdOzB/hQ=; b=JGbilGkhUqNCT7aYUu0mukbdHcUpk+2RoWXJEQnEEsrZ7A407Eo/69KpZY2/3qRw0zbIZv szaGbQqdDt4Xy2d6rWSw0F7vharo8ByqwYvM3AKjx241d62gfrxW0EzjND5f0O1vRHpUZn XQxFs6aSraJuCB2GtnYztvGpgEYdQdQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-1-WUkMC5nKOzGqhtjG1LndVg-1; Tue, 01 Dec 2020 11:54:32 -0500 X-MC-Unique: WUkMC5nKOzGqhtjG1LndVg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 98FBE84A5E0; Tue, 1 Dec 2020 16:54:30 +0000 (UTC) Received: from liberator.sandeen.net (ovpn04.gateway.prod.ext.phx2.redhat.com [10.5.9.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8E72210013C1; Tue, 1 Dec 2020 16:54:26 +0000 (UTC) To: torvalds@linux-foundation.org, Miklos Szeredi , Ira Weiny , David Howells Cc: linux-fsdevel@vger.kernel.org, linux-man@vger.kernel.org, linux-kernel@vger.kernel.org, xfs , linux-ext4@vger.kernel.org, Xiaoli Feng , Eric Sandeen From: Eric Sandeen Subject: [PATCH 0/2] statx: Fix DAX attribute collision and handling Message-ID: Date: Tue, 1 Dec 2020 10:54:26 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org There are two issues with the statx DAX attribute in the kernel today: 1) Its value clashes with STATX_ATTR_MOUNT_ROOT as dhowells previously reported 2) It is not set in the statx attributes_mask as reported by xifeng This short series changes the STATX_ATTR_DAX value, and moves the reporting from the vfs into the dax-capable filesystems so that they can set the statx atrributes_mask appropriately. Thanks, -Eric