lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 22 Jul 2022 15:49:45 +0700 From: Bagas Sanjaya <bagasdotme@...il.com> To: linux-doc@...r.kernel.org Cc: Heiko Carstens <hca@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>, Alexander Gordeev <agordeev@...ux.ibm.com>, Christian Borntraeger <borntraeger@...ux.ibm.com>, Sven Schnelle <svens@...ux.ibm.com>, Jonathan Corbet <corbet@....net>, Halil Pasic <pasic@...ux.ibm.com>, Tony Krowiak <akrowiak@...ux.ibm.com>, Jason Herne <jjherne@...ux.ibm.com>, linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org, Bagas Sanjaya <bagasdotme@...il.com>, Stephen Rothwell <sfr@...b.auug.org.au> Subject: [PATCH 6/8] Documentation: s390: escape *kvm->arch.crypto.pqap_hook pointer inside inline code The *kvm->arch.crypto.pqap_hook pointer triggers inline emphasis warning, due to unescaped asterisk. Escape it into inline code. Link: https://lore.kernel.org/linux-next/20220721201058.2a276286@canb.auug.org.au/ Fixes: e32d3827f3d5b2 ("s390/Docs: new doc describing lock usage by the vfio_ap device driver") Reported-by: Stephen Rothwell <sfr@...b.auug.org.au> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com> --- Documentation/s390/vfio-ap-locking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/s390/vfio-ap-locking.rst b/Documentation/s390/vfio-ap-locking.rst index 4194b78ace0e94..cfbb661ea72e63 100644 --- a/Documentation/s390/vfio-ap-locking.rst +++ b/Documentation/s390/vfio-ap-locking.rst @@ -107,7 +107,7 @@ The PQAP Hook Lock (arch/s390/include/asm/kvm_host.h) }; The PQAP Hook Lock is a r/w semaphore that controls access to the function -pointer of the handler (*kvm->arch.crypto.pqap_hook) to invoke when the +pointer of the handler (``*kvm->arch.crypto.pqap_hook``) to invoke when the PQAP(AQIC) instruction sub-function is intercepted by the host. The lock must be held in write mode when pqap_hook value is set, and in read mode when the pqap_hook function is called. -- An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists