From db80ea9b88628168d2bb7f17a60b73568a8ea102 Mon Sep 17 00:00:00 2001
From: Konstantin Belousov <kib@FreeBSD.org>
Date: Mon, 16 Feb 2026 12:18:07 +0200
Subject: [PATCH] pdfork.2: add EFAULT as possible error, explain some
 consequences of it

Reviewed by:	markj
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D55306
---
 lib/libsys/pdfork.2 | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/lib/libsys/pdfork.2 b/lib/libsys/pdfork.2
index 9cbeb65bc4f..49226cf069d 100644
--- a/lib/libsys/pdfork.2
+++ b/lib/libsys/pdfork.2
@@ -205,6 +205,24 @@ may return the same error numbers as
 .Xr fork 2 ) ,
 with the following additions:
 .Bl -tag -width Er
+.It Bq Er EFAULT
+The copyout of the resulting file descriptor value to the memory pointed
+to by
+.Fa fdp
+failed.
+.Pp
+Note that the child process was already created when this condition
+is detected,
+and the child continues execution, same as the parent.
+If this error must be handled, it is advisable to memoize the
+.Fn getpid
+result before the call to
+.Fn pdfork
+or
+.Fn pdrfork ,
+and compare it to the value returned by
+.Fn getpid
+after, to see if code is executing in parent or child.
 .It Bq Er EINVAL
 The signal number given to
 .Fn pdkill