From: Dan Williams <dan.j.williams@intel.com>
To: Jane Chu <jane.chu@oracle.com>, <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: RE: [PATCH v5 1/1] dax: enable dax fault handler to report VM_FAULT_HWPOISON
Date: Sat, 24 Jun 2023 22:51:42 -0700 [thread overview]
Message-ID: <6497d5ee65a8f_2ed729471@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230615181325.1327259-2-jane.chu@oracle.com>
Jane Chu wrote:
> When multiple processes mmap() a dax file, then at some point,
> a process issues a 'load' and consumes a hwpoison, the process
> receives a SIGBUS with si_code = BUS_MCEERR_AR and with si_lsb
> set for the poison scope. Soon after, any other process issues
> a 'load' to the poisoned page (that is unmapped from the kernel
> side by memory_failure), it receives a SIGBUS with
> si_code = BUS_ADRERR and without valid si_lsb.
>
> This is confusing to user, and is different from page fault due
> to poison in RAM memory, also some helpful information is lost.
>
> Channel dax backend driver's poison detection to the filesystem
> such that instead of reporting VM_FAULT_SIGBUS, it could report
> VM_FAULT_HWPOISON.
>
> If user level block IO syscalls fail due to poison, the errno will
> be converted to EIO to maintain block API consistency.
>
> Signed-off-by: Jane Chu <jane.chu@oracle.com>
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
next prev parent reply other threads:[~2023-06-25 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 18:13 [PATCH v5 0/1] dax: enable dax fault handler to report VM_FAULT_HWPOISON Jane Chu
2023-06-15 18:13 ` [PATCH v5 1/1] " Jane Chu
2023-06-25 5:51 ` Dan Williams [this message]
[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=6497d5ee65a8f_2ed729471@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=brauner@kernel.org \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=jane.chu@oracle.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).