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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2B257ECAAD3 for ; Mon, 5 Sep 2022 14:44:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238690AbiIEOoj (ORCPT ); Mon, 5 Sep 2022 10:44:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43610 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238407AbiIEOoD (ORCPT ); Mon, 5 Sep 2022 10:44:03 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 724B9167E8; Mon, 5 Sep 2022 07:42:37 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 68A1B68D05; Mon, 5 Sep 2022 16:42:29 +0200 (CEST) Date: Mon, 5 Sep 2022 16:42:28 +0200 From: Christoph Hellwig To: Dan Williams Cc: akpm@linux-foundation.org, djwong@kernel.org, Shiyang Ruan , Christoph Hellwig , Al Viro , Dave Chinner , Goldwyn Rodrigues , Jane Chu , Matthew Wilcox , Miaohe Lin , Naoya Horiguchi , Ritesh Harjani , nvdimm@lists.linux.dev, linux-xfs@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH 1/4] xfs: Quiet notify_failure EOPNOTSUPP cases Message-ID: <20220905144228.GA6784@lst.de> References: <166153426798.2758201.15108211981034512993.stgit@dwillia2-xfh.jf.intel.com> <166153427440.2758201.6709480562966161512.stgit@dwillia2-xfh.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <166153427440.2758201.6709480562966161512.stgit@dwillia2-xfh.jf.intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Fri, Aug 26, 2022 at 10:17:54AM -0700, Dan Williams wrote: > XFS always registers dax_holder_operations regardless of whether the > filesystem is capable of handling the notifications. The expectation is > that if the notify_failure handler cannot run then there are no > scenarios where it needs to run. In other words the expected semantic is > that page->index and page->mapping are valid for memory_failure() when > the conditions that cause -EOPNOTSUPP in xfs_dax_notify_failure() are > present. > > A fallback to the generic memory_failure() path is expected so do not > warn when that happens. Looks good: Reviewed-by: Christoph Hellwig