From: Kees Cook <keescook@chromium.org>
To: "Kenta.Tada@sony.com" <Kenta.Tada@sony.com>
Cc: amistry@google.com, samitolvanen@google.com, adobriyan@gmail.com,
elver@google.com, Kees Cook <keescook@chromium.org>,
paulmck@kernel.org, andreyknvl@google.com, rostedt@goodmis.org,
shorne@gmail.com, axboe@kernel.dk,
michael.weiss@aisec.fraunhofer.de, wad@chromium.org,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, luto@amacapital.net,
ebiederm@xmission.com, a.darwish@linutronix.de,
linux-fsdevel@vger.kernel.org, rppt@kernel.org
Subject: Re: [PATCH] seccomp: fix the cond to report loaded filters
Date: Sun, 21 Mar 2021 19:03:29 -0700 [thread overview]
Message-ID: <161637860542.4053241.2227340233601035129.b4-ty@chromium.org> (raw)
In-Reply-To: <OSBPR01MB26772D245E2CF4F26B76A989F5669@OSBPR01MB2677.jpnprd01.prod.outlook.com>
On Sun, 21 Mar 2021 15:52:19 +0000, Kenta.Tada@sony.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
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
prev parent reply other threads:[~2021-03-22 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 15:52 [PATCH] seccomp: fix the cond to report loaded filters Kenta.Tada
2021-03-22 2:03 ` Kees Cook [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=161637860542.4053241.2227340233601035129.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=Kenta.Tada@sony.com \
--cc=a.darwish@linutronix.de \
--cc=adobriyan@gmail.com \
--cc=amistry@google.com \
--cc=andreyknvl@google.com \
--cc=axboe@kernel.dk \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=michael.weiss@aisec.fraunhofer.de \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=shorne@gmail.com \
--cc=wad@chromium.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).