From: Aleksandr Nogikh <a.nogikh@gmail.com>
To: jmorris@namei.org
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
akinobu.mita@gmail.com, Andrey Konovalov <andreyknvl@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Marco Elver <elver@google.com>,
Alexander Potapenko <glider@google.com>,
Kees Cook <keescook@google.com>,
casey@schaufler-ca.com, penguin-kernel@i-love.sakura.ne.jp,
LKML <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org, mortonm@chromium.org,
Aleksandr Nogikh <nogikh@google.com>
Subject: Re: [PATCH v4 0/2] security: add fault injection to LSM hooks
Date: Thu, 19 Nov 2020 00:20:52 +0300 [thread overview]
Message-ID: <CADpXja_NZqMomnHfzRRNE97LwP4WYZY4Z1egeFiCjwSbea-Urg@mail.gmail.com> (raw)
In-Reply-To: <20201111104409.1530957-1-a.nogikh@gmail.com>
On Wed, 11 Nov 2020 at 13:44, Aleksandr Nogikh <a.nogikh@gmail.com> wrote:
>
> From: Aleksandr Nogikh <nogikh@google.com>
>
> Fault injection capabilities[Documentation/fault-injection/fault-injection.rst]
> facilitate testing of the stability of the Linux kernel by providing
> means to force a number of kernel interfaces to return error
> codes. This patch series proposes adding such fault injection
> capability into LSM hooks.
>
> The intent is to make it possible to test whether the existing kernel
> code properly handles negative return values of LSM hooks. Syzbot
> [https://github.com/google/syzkaller/blob/master/docs/syzbot.md] will
> automatically do that with the aid of instrumentation tools once these
> changes are merged.
[...]
James, can you please take another look at the series? Are there
enough reviewed-bys now?
--
Best Regards,
Aleksandr
prev parent reply other threads:[~2020-11-18 21:21 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 ` [PATCH v4 2/2] docs: add fail_lsm_hooks info to fault-injection.rst Aleksandr Nogikh
2020-11-18 21:20 ` Aleksandr Nogikh [this message]
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=CADpXja_NZqMomnHfzRRNE97LwP4WYZY4Z1egeFiCjwSbea-Urg@mail.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.