Lines Matching refs:landlock

22 looking for "landlock: Up and running" in kernel logs (as root):
23 ``dmesg | grep landlock || journalctl -kb -g landlock`` .
225 Full working code can be found in `samples/landlock/sandboxer.c`_.
444 .. kernel-doc:: include/uapi/linux/landlock.h
450 .. kernel-doc:: security/landlock/syscalls.c
453 .. kernel-doc:: include/uapi/linux/landlock.h
459 .. kernel-doc:: security/landlock/syscalls.c
462 .. kernel-doc:: include/uapi/linux/landlock.h
469 .. kernel-doc:: security/landlock/syscalls.c
604 sys_landlock_restrict_self().  See Documentation/admin-guide/LSM/landlock.rst
619 contain ``CONFIG_LSM=landlock,[...]`` with ``[...]``  as the list of other
626 If the running kernel does not have ``landlock`` in ``CONFIG_LSM``, then we can
627 enable Landlock by adding ``lsm=landlock,[...]`` to
638 ...and if the cmdline doesn't contain ``landlock`` either:
646 list with the ``landlock,`` prefix::
648   lsm=landlock,lockdown,yama,integrity,apparmor
655     # dmesg | grep landlock || journalctl -kb -g landlock
656     [    0.000000] Command line: [...] lsm=landlock,lockdown,yama,integrity,apparmor
657     [    0.000000] Kernel command line: [...] lsm=landlock,lockdown,yama,integrity,apparmor
658     [    0.000000] LSM: initializing lsm=lockdown,capability,landlock,yama,integrity,apparmor
659     [    0.000000] landlock: Up and running.
699 Documentation/admin-guide/LSM/landlock.rst
704 * Documentation/admin-guide/LSM/landlock.rst
705 * Documentation/security/landlock.rst
706 * https://landlock.io
709 .. _samples/landlock/sandboxer.c:
710 … https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/samples/landlock/sandboxer.c