From: Kees Cook <keescook@chromium.org>
To: Jann Horn <jannh@google.com>
Cc: Kees Cook <keescook@chromium.org>, Tyler Hicks <code@tyhicks.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, Will Drewry <wad@chromium.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH v2] seccomp: Remove bogus __user annotations
Date: Fri, 20 Nov 2020 11:40:24 -0800 [thread overview]
Message-ID: <160590121736.3376343.9881262449141772131.b4-ty@chromium.org> (raw)
In-Reply-To: <20201120170545.1419332-1-jannh@google.com>
On Fri, 20 Nov 2020 18:05:45 +0100, Jann Horn wrote:
> Buffers that are passed to read_actions_logged() and write_actions_logged()
> are in kernel memory; the sysctl core takes care of copying from/to
> userspace.
Applied to for-next/seccomp, thanks!
[1/1] seccomp: Remove bogus __user annotations
https://git.kernel.org/kees/c/fab686eb0307
--
Kees Cook
prev parent reply other threads:[~2020-11-20 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 17:05 [PATCH v2] seccomp: Remove bogus __user annotations Jann Horn
2020-11-20 19:40 ` 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=160590121736.3376343.9881262449141772131.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=code@tyhicks.com \
--cc=hch@lst.de \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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 NNTP newsgroup(s).