linux-kernel - Re: [PATCH v3 0/2] security: add fault injection to LSM hooks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFSQ=y455bVOGMpRW86Gto+WdL1idxSXM0RPifokEotyg2ccjg@mail.gmail.com>
Date:   Mon, 9 Nov 2020 22:06:27 +0300
From:   Aleksandr Nogikh <aleksandrnogikh@...il.com>
To:     jmorris@...ei.org, serge@...lyn.com, akinobu.mita@...il.com
Cc:     Andrey Konovalov <andreyknvl@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Marco Elver <elver@...gle.com>,
        Alexander Potapenko <glider@...gle.com>,
        Kees Cook <keescook@...gle.com>, casey@...aufler-ca.com,
        linux-kernel@...r.kernel.org,
        linux-security-module@...r.kernel.org,
        Aleksandr Nogikh <nogikh@...gle.com>, mortonm@...omium.org
Subject: Re: [PATCH v3 0/2] security: add fault injection to LSM hooks

On Thu, 29 Oct 2020 at 21:35, Aleksandr Nogikh
<aleksandrnogikh@...il.com> wrote:
>
> From: Aleksandr Nogikh <nogikh@...gle.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?

Is there anyone else who is not on the recipient list but still might
be interested in the series?