From: Aleksandr Nogikh <a.nogikh@gmail.com>
To: jmorris@namei.org, serge@hallyn.com, akinobu.mita@gmail.com
Cc: andreyknvl@google.com, dvyukov@google.com, elver@google.com,
glider@google.com, keescook@google.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Aleksandr Nogikh <nogikh@google.com>
Subject: [RFC PATCH v2 2/2] docs: add fail_lsm_hooks info to fault-injection.rst
Date: Mon, 26 Oct 2020 12:52:27 +0000 [thread overview]
Message-ID: <20201026125227.54520-3-a.nogikh@gmail.com> (raw)
In-Reply-To: <20201026125227.54520-1-a.nogikh@gmail.com>
From: Aleksandr Nogikh <nogikh@google.com>
Describe fail_lsm_hooks fault injection capability.
Signed-off-by: Aleksandr Nogikh <nogikh@google.com>
---
v2:
- Added this commit.
---
Documentation/fault-injection/fault-injection.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/fault-injection/fault-injection.rst b/Documentation/fault-injection/fault-injection.rst
index 31ecfe44e5b4..48705adfbc18 100644
--- a/Documentation/fault-injection/fault-injection.rst
+++ b/Documentation/fault-injection/fault-injection.rst
@@ -48,6 +48,12 @@ Available fault injection capabilities
status code is NVME_SC_INVALID_OPCODE with no retry. The status code and
retry flag can be set via the debugfs.
+- fail_lsm_hooks
+
+ injects failures into LSM hooks. When a fault is injected, actual hooks
+ are not executed and a code from /sys/kernel/debug/fail_lsm_hooks/retval
+ is returned (the default value is -EACCES).
+
Configure fault-injection capabilities behavior
-----------------------------------------------
--
2.29.0.rc1.297.gfa9743e501-goog
next prev parent reply other threads:[~2020-10-26 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 12:52 [RFC PATCH v2 0/2] security: add fault injection to LSM hooks Aleksandr Nogikh
2020-10-26 12:52 ` [RFC PATCH v2 1/2] security: add fault injection capability Aleksandr Nogikh
2020-10-26 16:20 ` Casey Schaufler
2020-10-27 17:29 ` Aleksandr Nogikh
2020-10-27 17:56 ` Casey Schaufler
2020-10-26 12:52 ` Aleksandr Nogikh [this message]
2020-10-27 15:31 ` [RFC PATCH v2 2/2] docs: add fail_lsm_hooks info to fault-injection.rst Akinobu Mita
2020-10-27 17:33 ` Aleksandr Nogikh
2020-10-28 9:41 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201026125227.54520-3-a.nogikh@gmail.com \
--to=a.nogikh@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=jmorris@namei.org \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nogikh@google.com \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).