Merging upstream version 6.7.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 9 insertions, 9 deletions

diff --git a/man7/user-session-keyring.7 b/man7/user-session-keyring.7
index 3fc8795..7af56f0 100644
--- a/man7/user-session-keyring.7
+++ b/man7/user-session-keyring.7
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH user-session-keyring 7 2023-02-05 "Linux man-pages 6.05.01"
+.TH user-session-keyring 7 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 user-session-keyring \- per-user default session keyring
 .SH DESCRIPTION
@@ -15,7 +15,7 @@ The user session keyring has a name (description) of the form
 where
 .I <UID>
 is the user ID of the corresponding user.
-.PP
+.P
 The user session keyring is associated with the record that
 the kernel maintains for the UID.
 It comes into existence upon the first attempt to access either the
@@ -28,7 +28,7 @@ The keyring remains pinned in existence so long as there are processes
 running with that real UID or files opened by those processes remain open.
 (The keyring can also be pinned indefinitely by linking it
 into another keyring.)
-.PP
+.P
 The user session keyring is created on demand when a thread requests it
 or when a thread asks for its
 .BR session\-keyring (7)
@@ -36,22 +36,22 @@ and that keyring doesn't exist.
 In the latter case, a user session keyring will be created and,
 if the session keyring wasn't to be created,
 the user session keyring will be set as the process's actual session keyring.
-.PP
+.P
 The user session keyring is searched by
 .BR request_key (2)
 if the actual session keyring does not exist and is ignored otherwise.
-.PP
+.P
 A special serial number value,
 .BR KEY_SPEC_USER_SESSION_KEYRING ,
 is defined
 that can be used in lieu of the actual serial number of
 the calling process's user session keyring.
-.PP
+.P
 From the
 .BR keyctl (1)
 utility, '\fB@us\fP' can be used instead of a numeric key ID in
 much the same way.
-.PP
+.P
 User session keyrings are independent of
 .BR clone (2),
 .BR fork (2),
@@ -61,10 +61,10 @@ and
 .BR _exit (2)
 excepting that the keyring is destroyed when the UID record is destroyed
 when the last process pinning it exits.
-.PP
+.P
 If a user session keyring does not exist when it is accessed,
 it will be created.
-.PP
+.P
 Rather than relying on the user session keyring,
 it is strongly recommended\[em]especially if the process
 is running as root\[em]that a