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, casey@schaufler-ca.com,
penguin-kernel@i-love.sakura.ne.jp, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, mortonm@chromium.org,
Aleksandr Nogikh <nogikh@google.com>
Subject: [PATCH v4 2/2] docs: add fail_lsm_hooks info to fault-injection.rst
Date: Wed, 11 Nov 2020 10:44:09 +0000 [thread overview]
Message-ID: <20201111104409.1530957-3-a.nogikh@gmail.com> (raw)
In-Reply-To: <20201111104409.1530957-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.2.222.g5d2a92d10f8-goog
next prev parent reply other threads:[~2020-11-11 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 10:44 [PATCH v4 0/2] security: add fault injection to LSM hooks Aleksandr Nogikh
2020-11-11 10:44 ` [PATCH v4 1/2] security: add fault injection capability Aleksandr Nogikh
2020-11-11 11:48 ` Alexander Potapenko
2020-11-11 10:44 ` Aleksandr Nogikh [this message]
2020-11-18 21:20 ` [PATCH v4 0/2] security: add fault injection to LSM hooks Aleksandr Nogikh
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=20201111104409.1530957-3-a.nogikh@gmail.com \
--to=a.nogikh@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=andreyknvl@google.com \
--cc=casey@schaufler-ca.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=mortonm@chromium.org \
--cc=nogikh@google.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.