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=-1.5 required=3.0 tests=BAYES_50,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 6F3E7C433E2 for ; Wed, 2 Sep 2020 16:04:44 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3D868207EA for ; Wed, 2 Sep 2020 16:04:44 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Grne77LD" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3D868207EA Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvdimm-bounces@lists.01.org Received: from ml01.vlan13.01.org (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id F304813AA0E3E; Wed, 2 Sep 2020 09:04:43 -0700 (PDT) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=205.139.110.61; helo=us-smtp-delivery-1.mimecast.com; envelope-from=msnitzer@redhat.com; receiver= Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 3809613AA0DD9 for ; Wed, 2 Sep 2020 09:04:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1599062679; 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; bh=a2m4PpGgyTZJzBhQIkW7LGiGRcC2yittbMPRgbM5xgg=; b=Grne77LDVJBBOlqGXlfFFzOzL0olT6ceRqo5dLCG2EmJE3PfgnUugWlQAj/lRyKm4O4xJ+ y6GEIhxAjObgmgNeayKv6weus6KklJ3kFdDQ/MGZuq7pQaPw5TSTk168JF/uylDmi8jpjc 7FrLaoKVhkwCAi3Ky7Og35n+Lt5y0hs= 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-334-lyti-e-JNCWu1rLqCVMDhA-1; Wed, 02 Sep 2020 12:04:37 -0400 X-MC-Unique: lyti-e-JNCWu1rLqCVMDhA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 122BA801AB2; Wed, 2 Sep 2020 16:04:36 +0000 (UTC) Received: from localhost (unknown [10.18.25.174]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 302D561983; Wed, 2 Sep 2020 16:04:33 +0000 (UTC) Date: Wed, 2 Sep 2020 12:04:32 -0400 From: Mike Snitzer To: Coly Li , Jan Kara , Ira Weiny , Pankaj Gupta , Vishal Verma Subject: flood of "dm-X: error: dax access failed" due to 5.9 commit 231609785cbfb Message-ID: <20200902160432.GA5513@redhat.com> MIME-Version: 1.0 User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=msnitzer@redhat.com X-Mimecast-Spam-Score: 0.002 X-Mimecast-Originator: redhat.com Content-Disposition: inline Message-ID-Hash: P4GSVN2RET6T6DBRCOJPLB4OWZIAVAJQ X-Message-ID-Hash: P4GSVN2RET6T6DBRCOJPLB4OWZIAVAJQ X-MailFrom: msnitzer@redhat.com X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation CC: linux-nvdimm@lists.01.org, dm-devel@redhat.com X-Mailman-Version: 3.1.1 Precedence: list List-Id: "Linux-nvdimm developer list." Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 5.9 commit 231609785cbfb ("dax: print error message by pr_info() in __generic_fsdax_supported()") switched from pr_debug() to pr_info(). The justification in the commit header is really inadequate. If there is a problem that you need to drill in on, repeat the testing after enabling the dynamic debugging. Otherwise, now all DM devices that aren't layered on DAX capable devices spew really confusing noise to users when they simply activate their non-DAX DM devices: [66567.129798] dm-6: error: dax access failed (-5) [66567.134400] dm-6: error: dax access failed (-5) [66567.139152] dm-6: error: dax access failed (-5) [66567.314546] dm-2: error: dax access failed (-95) [66567.319380] dm-2: error: dax access failed (-95) [66567.324254] dm-2: error: dax access failed (-95) [66567.479025] dm-2: error: dax access failed (-95) [66567.483713] dm-2: error: dax access failed (-95) [66567.488722] dm-2: error: dax access failed (-95) [66567.494061] dm-2: error: dax access failed (-95) [66567.498823] dm-2: error: dax access failed (-95) [66567.503693] dm-2: error: dax access failed (-95) commit 231609785cbfb must be reverted. Please advise, thanks. Mike _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org