Break the text up a little, to improve readability.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
although use of this operation is only suitable for applications that are
trusted to maintain any desired separation between the old and new security
contexts.
+.IP
Prior to Linux 2.6.28, SELinux did not allow threads within a
multi-threaded process to set their security context via this node
as it would yield an inconsistency among the security contexts of the
security context, where the bounded relation is defined in policy and
guarantees that the new security context has a subset of the permissions
of the old security context.
+.IP
Other security modules may choose to support "set" operations via
writes to this node.
.TP