From: James Morris <jmorris@namei.org>
To: Aleksandr Nogikh <aleksandrnogikh@gmail.com>
Cc: 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, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Aleksandr Nogikh <nogikh@google.com>,
mortonm@chromium.org
Subject: Re: [PATCH v3 0/2] security: add fault injection to LSM hooks
Date: Tue, 10 Nov 2020 14:14:55 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.2011101414330.30138@namei.org> (raw)
In-Reply-To: <CAFSQ=y455bVOGMpRW86Gto+WdL1idxSXM0RPifokEotyg2ccjg@mail.gmail.com>
On Mon, 9 Nov 2020, Aleksandr Nogikh wrote:
> On Thu, 29 Oct 2020 at 21:35, Aleksandr Nogikh
> <aleksandrnogikh@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.
> > [...]
>
> What tree should these changes go to?
>
Mine, but more signoffs/acks are required.
> Is there anyone else who is not on the recipient list but still might
> be interested in the series?
>
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2020-11-10 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 18:35 [PATCH v3 0/2] security: add fault injection to LSM hooks Aleksandr Nogikh
2020-10-29 18:35 ` [PATCH v3 1/2] security: add fault injection capability Aleksandr Nogikh
2020-11-02 14:03 ` Marco Elver
2020-11-10 4:43 ` Tetsuo Handa
2020-11-10 18:35 ` Aleksandr Nogikh
2020-11-10 17:42 ` Andrey Konovalov
2020-10-29 18:35 ` [PATCH v3 2/2] docs: add fail_lsm_hooks info to fault-injection.rst Aleksandr Nogikh
2020-11-09 19:06 ` [PATCH v3 0/2] security: add fault injection to LSM hooks Aleksandr Nogikh
2020-11-10 3:14 ` James Morris [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=alpine.LRH.2.21.2011101414330.30138@namei.org \
--to=jmorris@namei.org \
--cc=akinobu.mita@gmail.com \
--cc=aleksandrnogikh@gmail.com \
--cc=andreyknvl@google.com \
--cc=casey@schaufler-ca.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--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=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).