From: Jane Chu <jane.chu@oracle.com>
To: dan.j.williams@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, ira.weiny@intel.com, willy@infradead.org,
viro@zeniv.linux.org.uk, brauner@kernel.org,
nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v5 0/1] dax: enable dax fault handler to report VM_FAULT_HWPOISON
Date: Thu, 15 Jun 2023 12:13:24 -0600 [thread overview]
Message-ID: <20230615181325.1327259-1-jane.chu@oracle.com> (raw)
Change from v4:
Add comments describing when and why dax_mem2blk_err() is used.
Suggested by Dan.
Change from v3:
Prevent leaking EHWPOISON to user level block IO calls such as
zero_range_range, and truncate. Suggested by Dan.
Change from v2:
Convert EHWPOISON to EIO to prevent EHWPOISON errno from leaking
out to block read(2). Suggested by Matthew.
Jane Chu (1):
dax: enable dax fault handler to report VM_FAULT_HWPOISON
drivers/dax/super.c | 5 ++++-
drivers/nvdimm/pmem.c | 2 +-
drivers/s390/block/dcssblk.c | 3 ++-
fs/dax.c | 11 ++++++-----
fs/fuse/virtio_fs.c | 3 ++-
include/linux/dax.h | 13 +++++++++++++
include/linux/mm.h | 2 ++
7 files changed, 30 insertions(+), 9 deletions(-)
--
2.18.4
next reply other threads:[~2023-06-15 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 18:13 Jane Chu [this message]
2023-06-15 18:13 ` [PATCH v5 1/1] dax: enable dax fault handler to report VM_FAULT_HWPOISON Jane Chu
2023-06-25 5:51 ` Dan Williams
[not found] ` <b57afc45-6bf8-3849-856f-2873e60fcf97@web.de>
2023-06-26 17:49 ` [PATCH v5 0/1] " Jane Chu
[not found] ` <be3db57c-29d0-cfc9-f0cc-1765b672c57e@web.de>
2023-06-27 15:22 ` [v5 " Matthew Wilcox
[not found] ` <b46b90b5-cc1d-9311-892b-a0f8abe155d6@web.de>
2023-06-27 16:24 ` Matthew Wilcox
[not found] ` <ba6d2b6b-87b8-29c9-93a9-0026ee7ae7ca@web.de>
2023-06-27 17:25 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230615181325.1327259-1-jane.chu@oracle.com \
--to=jane.chu@oracle.com \
--cc=brauner@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).