[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161637860542.4053241.2227340233601035129.b4-ty@chromium.org>
Date: Sun, 21 Mar 2021 19:03:29 -0700
From: Kees Cook <keescook@...omium.org>
To: "Kenta.Tada@...y.com" <Kenta.Tada@...y.com>
Cc: Kees Cook <keescook@...omium.org>, wad@...omium.org,
christian.brauner@...ntu.com, ebiederm@...ssion.com,
linux-kernel@...r.kernel.org, axboe@...nel.dk,
gladkov.alexey@...il.com, avagin@...il.com, paulmck@...nel.org,
elver@...gle.com, a.darwish@...utronix.de, amistry@...gle.com,
linux-fsdevel@...r.kernel.org, andreyknvl@...gle.com,
samitolvanen@...gle.com, michael.weiss@...ec.fraunhofer.de,
rostedt@...dmis.org, peterz@...radead.org, luto@...capital.net,
rppt@...nel.org, shorne@...il.com, adobriyan@...il.com,
containers@...ts.linux-foundation.org
Subject: Re: [PATCH] seccomp: fix the cond to report loaded filters
On Sun, 21 Mar 2021 15:52:19 +0000, Kenta.Tada@...y.com wrote:
> Strictly speaking, seccomp filters are only used
> when CONFIG_SECCOMP_FILTER.
> This patch fixes the condition to enable "Seccomp_filters"
> in /proc/$pid/status.
Applied to for-next/seccomp, thanks!
[1/1] seccomp: fix the cond to report loaded filters
https://git.kernel.org/kees/c/15a2fd51384a
--
Kees Cook
Powered by blists - more mailing lists