Received: by 2002:a05:6a10:eb17:0:0:0:0 with SMTP id hx23csp16761pxb; Wed, 8 Sep 2021 16:22:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxMzW58cCR/9eRvud3n38zEF/90pm/i/uEHSlRKbIa/lSN1j/N1btVeCSXQhbYgGDLGAApk X-Received: by 2002:a17:906:8399:: with SMTP id p25mr117728ejx.449.1631143331194; Wed, 08 Sep 2021 16:22:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631143331; cv=none; d=google.com; s=arc-20160816; b=GOzVdGmyp/6xIPdBSngECG2kH6SbL+D232cvMVfEqCx9HhNqmbLj/QMUdmUEIIYLYN 6uuazH+kNbnKlZwAX16xIqeGxWYcut9M4TSRz0z0fv5m1dlTk9Wd4POWBz+9/DzT7bN8 lvIX00HUyhbYju3K39gRrIZZIrzPsmz7mzxSeRrg5pM7by2dp2gnh2hv8b9W/L+DYxys LbT/WRTJfrITgIaF/55I0+sFmAFN0FhwdWFGtxvxlvSbW3DIae//A6Zwg+VwU9LsIdQC NH5Z4i5dT09o33OIx3w5bg92zZ3ROvxapJtRaVOtSl1hcUn6SaodFOz2mSg6niS6PZRg csKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:mime-version :dkim-signature; bh=sW4NTlq7SSKyyy7HoR/7gu1f7/0aKhJl18M8jx83+dY=; b=MenVxFLR/KTjV0RtbEsRmh/4FfyBD8ei/u6K+oCzwqvwfykHdTQ0iNWiFhKTUtsscS rkFa3DV6oasTFhh26bFd3V/Y6fZLM0GqomAU0jDLWoOrEpTg+nhj8ZJkDq49r5d++xWp CoJThOrdLxGNQpfuduclEhSM/EgBMeGlMhxZRudmeN5sQJ0QavhKyNntV+YhwSQq0uTF RhEfNtN42g8I3/zKSb2TUzkKOHk4l0Q/J6R9EmNifA5Y00JE0VnIBrv4vnTIpK1HbYqL L/1pnSDMxizjwB3C9/eJ5lprWZQL5O2E+Z2Tu02JBcaleRRXclXXdN28Wd6TjsKQhjHo y24g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=s33R3Ifq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d11si50989edm.533.2021.09.08.16.21.34; Wed, 08 Sep 2021 16:22:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=s33R3Ifq; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235903AbhIHXTu (ORCPT + 99 others); Wed, 8 Sep 2021 19:19:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38794 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233315AbhIHXTu (ORCPT ); Wed, 8 Sep 2021 19:19:50 -0400 Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EF06DC061575 for ; Wed, 8 Sep 2021 16:18:39 -0700 (PDT) Received: by mail-pf1-x430.google.com with SMTP id x7so69856pfa.8 for ; Wed, 08 Sep 2021 16:18:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=sW4NTlq7SSKyyy7HoR/7gu1f7/0aKhJl18M8jx83+dY=; b=s33R3IfqxOpVYyZFcZ0cBjmgnfKK7bpLevNSo4k5JhEkapQc71J9n6IBQPhY9jgV3K DsRqc76lt1eXDNCRB0LZ5giVDA4S/MtOHPBV5POPxC28AS4SnIqaRVtBHH6q0yuGttW+ 7jnhJZ7h6jgcqj6/soP/npvR7JOOqM81CBfghzUGJSSOcHNDTS71M/DpIAqwtlnHV4UC GxNDVfJBFyTYgKiUDIY8dFfk91E7detUxRm1IByqrm2oMsq7yGIxOl/SjO651BzLSBnJ iceyoR8bM5FRH83y4hMvnXMacgufn4LdY+2ssRQPsgZVMbnKqfONPyt37c1xyvluAxJI vbRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=sW4NTlq7SSKyyy7HoR/7gu1f7/0aKhJl18M8jx83+dY=; b=gwEgEDyndmPxmUIy1Bc+IgjyPXzpOfKbrLg5nvxtEjHaqsbOldDURfoWmBvrWX/RdF hWVPnjaZOb82sNH5+nm1ZUJJW7guTdpMC4fFgCMaDM5u1zQEw1i7mHSgd6R4GeUKZwz3 SVCulJCl2nXnydPzDHUAeIDZmZNCha7h8NypbPNRARUHO3L0E/gbhhuGTwXoms8Ow7YK OZ1HfEGEtAldcmjLfM9bNcI0UXLFUHrnaZZwBM5s+AvjMaa2zQjelPiMEZAkcuHkXklg lCJ2DC6oB/2ss+XVv2qOLuZPnxXHVaVc4O0xBOKnT+MrVs4ATiSDidjVsz8Cq7glHht5 KPDg== X-Gm-Message-State: AOAM532YwLdD09MiQbMymdKQLYN+6cXa9kzsQQm+bOE5HcsVZG+lVQdh EUVVE5CmwQve14ZlQhDfxVxsg+CO99kkaTJMyvOfYb0IhvHZkw== X-Received: by 2002:a63:3545:: with SMTP id c66mr528820pga.377.1631143119383; Wed, 08 Sep 2021 16:18:39 -0700 (PDT) MIME-Version: 1.0 From: Dan Williams Date: Wed, 8 Sep 2021 16:18:28 -0700 Message-ID: Subject: [GIT PULL] libnvdimm / persistent memory update for v5.15 To: Linus Torvalds Cc: Linux NVDIMM , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-5.15 ...to receive the libnvdimm update for v5.15. It includes a bug fix for a long standing race in the driver shutdown path. More people are stress testing the nvdimm configuration mechanism which is a welcome sign. There is also a rework of the infrastructure for looking up the dax_device associated with a block_device. This collided (silent conflict) with the erofs updates to add dax support this cycle. Gao Xiang noted this as well in the erofs pull request. Stephen's fix [1] looked correct to me. Otherwise, it has been in -next for a while with no other reported issues. Please pull, thanks, Dan [1]: https://lore.kernel.org/r/20210830170938.6fd8813d@canb.auug.org.au --- The following changes since commit e22ce8eb631bdc47a4a4ea7ecf4e4ba499db4f93: Linux 5.14-rc7 (2021-08-22 14:24:56 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-5.15 for you to fetch changes up to 3fc3725357414636d91be1558ce8b14f228b4bda: Merge branch 'for-5.15/fsdax-cleanups' into for-5.15/libnvdimm (2021-09-08 15:58:13 -0700) ---------------------------------------------------------------- libnvdimm for v5.15 - Fix a race condition in the teardown path of raw mode pmem namespaces. - Cleanup the code that filesystems use to detect filesystem-dax capabilities of their underlying block device. ---------------------------------------------------------------- Christoph Hellwig (9): fsdax: improve the FS_DAX Kconfig description and help text dax: stop using bdevname dm: use fs_dax_get_by_bdev instead of dax_get_by_host dax: mark dax_get_by_host static dax: move the dax_read_lock() locking into dax_supported dax: remove __generic_fsdax_supported dax: stub out dax_supported for !CONFIG_FS_DAX xfs: factor out a xfs_buftarg_is_dax helper dax: remove bdev_dax_supported Dan Williams (1): Merge branch 'for-5.15/fsdax-cleanups' into for-5.15/libnvdimm sumiyawang (1): libnvdimm/pmem: Fix crash triggered when I/O in-flight during unbind drivers/dax/super.c | 191 +++++++++++++++++++------------------------------- drivers/md/dm-table.c | 9 +-- drivers/md/dm.c | 2 +- drivers/nvdimm/pmem.c | 4 +- fs/Kconfig | 21 +++++- fs/ext2/super.c | 3 +- fs/ext4/super.c | 3 +- fs/xfs/xfs_super.c | 16 +++-- include/linux/dax.h | 41 ++--------- 9 files changed, 119 insertions(+), 171 deletions(-)