> Thanks. I've applied the patch, but I made a few tweaks afterwards, > as per the patch below. Notably, I changed "message" to > "notification", since that seems more consistent with the > language in the rest of the page. Is it okay, Peter? Hmmm -- ignore this. For now, I reverted the patch below, since it causes the following patch to break. Cheers, Michael > diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2 > index 8245253c3..eb2c6d5f9 100644 > --- a/man2/userfaultfd.2 > +++ b/man2/userfaultfd.2 > @@ -78,8 +78,10 @@ all memory ranges that were registered with the object are unregistered > and unread events are flushed. > .\" > .PP > -Since Linux 4.14, userfaultfd page fault message can selectively embed > -faulting thread ID information into the fault message. > +Since Linux 4.14, > +.\" commit 9d4ac934829ac58c5109c49e6dfe677300e5e652 > +a userfaultfd page fault notification can selectively embed the > +faulting thread ID information in the notification. > One needs to enable this feature explicitly using the > .B UFFD_FEATURE_THREAD_ID > feature bit when initializing the userfaultfd context. > > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
