From: Peter Xu <peterx@redhat.com>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Jiaqi Yan <jiaqiyan@google.com>,
James Houghton <jthoughton@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
David Hildenbrand <david@redhat.com>,
Hongchen Zhang <zhanghongchen@loongson.cn>,
Huang Ying <ying.huang@intel.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Miaohe Lin <linmiaohe@huawei.com>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
Nadav Amit <namit@vmware.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
Shuah Khan <shuah@kernel.org>,
ZhangPeng <zhangpeng362@huawei.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
Anish Moorthy <amoorthy@google.com>
Subject: Re: [PATCH 1/3] mm: userfaultfd: add new UFFDIO_SIGBUS ioctl
Date: Thu, 18 May 2023 17:50:56 -0400 [thread overview]
Message-ID: <ZGadwEDlsvIxnsvq@x1n> (raw)
In-Reply-To: <ZGaaxjS4jWUio+f6@x1n>
On Thu, May 18, 2023 at 05:38:14PM -0400, Peter Xu wrote:
> If with uffd, perhaps avoid calling it sigbus? As we have FEATURE_SIGBUS
> and I'm afraid it'll cause confusion. UFFDIO_HWPOISON may sound more
> suitable?
Or UFFDIO_POISON (to identify it from real hw poisons)..
--
Peter Xu
next prev parent reply other threads:[~2023-05-18 21:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 18:24 [PATCH 1/3] mm: userfaultfd: add new UFFDIO_SIGBUS ioctl Axel Rasmussen
2023-05-11 18:24 ` [PATCH 2/3] selftests/mm: refactor uffd_poll_thread to allow custom fault handlers Axel Rasmussen
2023-05-11 18:24 ` [PATCH 3/3] selftests/mm: add uffd unit test for UFFDIO_SIGBUS Axel Rasmussen
2023-05-11 20:22 ` [PATCH 1/3] mm: userfaultfd: add new UFFDIO_SIGBUS ioctl Mike Kravetz
2023-05-11 20:40 ` Axel Rasmussen
2023-05-11 21:05 ` Axel Rasmussen
2023-05-11 22:00 ` James Houghton
2023-05-17 22:12 ` Peter Xu
2023-05-17 22:20 ` Peter Xu
2023-05-17 22:28 ` Axel Rasmussen
2023-05-18 0:20 ` Peter Xu
2023-05-18 0:43 ` Jiaqi Yan
2023-05-18 16:05 ` Peter Xu
2023-05-18 20:38 ` Axel Rasmussen
2023-05-18 21:38 ` Peter Xu
2023-05-18 21:50 ` Peter Xu [this message]
2023-05-19 8:38 ` David Hildenbrand
2023-05-19 15:04 ` Jiaqi Yan
2023-05-19 16:20 ` Peter Xu
2023-05-19 17:32 ` Axel Rasmussen
2023-05-23 17:27 ` Peter Xu
2023-05-23 17:26 ` Peter Xu
2023-05-23 17:59 ` Axel Rasmussen
2023-05-24 15:05 ` Peter Xu
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=ZGadwEDlsvIxnsvq@x1n \
--to=peterx@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=amoorthy@google.com \
--cc=axelrasmussen@google.com \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=namit@vmware.com \
--cc=naoya.horiguchi@nec.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=ying.huang@intel.com \
--cc=zhanghongchen@loongson.cn \
--cc=zhangpeng362@huawei.com \
/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).