From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Paolo Bonzini <pbonzini@redhat.com>,
David Windsor <dave@nullcore.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] usercopy whitelisting for v4.15-rc1
Date: Mon, 20 Nov 2017 19:50:27 +0000 [thread overview]
Message-ID: <20171120195027.GA20045@srcf.ucam.org> (raw)
In-Reply-To: <CA+55aFykjza0H5ytZH_aJKYs9tC84OLyVT30--cvo0mpAzpWaA@mail.gmail.com>
On Fri, Nov 17, 2017 at 01:13:10PM -0800, Linus Torvalds wrote:
> So the hardening efforts should instead _start_ from the standpoint of
> "let's warn about what looks dangerous, and maybe in a _year_ when
> we've warned for a long time, and we are confident that we've actually
> caught all the normal cases, _then_ we can start taking more drastic
> measures".
Can you clarify a little with regard to how you'd have liked this
patchset to look? With
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=usercopy-v4.15-rc1&id=93edfb33387772a9ae7693ddf9811280ffc4025b
it seems pretty like we're at the end goal you've described (default to
a mode that generates a warning rather than returning an error), so is
it just that this appeared at the end of the patchset development
process rather than being there from the beginning?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2017-11-20 20:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 16:54 [GIT PULL] usercopy whitelisting for v4.15-rc1 Kees Cook
2017-11-17 17:35 ` Linus Torvalds
2017-11-17 17:45 ` Paolo Bonzini
2017-11-17 20:35 ` Kees Cook
2017-11-17 21:13 ` Linus Torvalds
2017-11-17 22:19 ` Kees Cook
2017-11-20 19:50 ` Matthew Garrett [this message]
[not found] ` <CA+55aFyMtpYASreqGuRmJoB8isJnhOxsWMa4uoQu6WtBJDHU6A@mail.gmail.com>
2017-11-20 23:29 ` Matthew Garrett
2017-11-21 0:42 ` Kees Cook
2017-11-21 13:53 ` Lukas Wunner
2017-11-21 17:22 ` Randy Dunlap
2017-11-21 14:34 ` Linus Torvalds
2017-11-21 13:48 ` Jason A. Donenfeld
2017-11-21 15:25 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2017-11-13 7:29 Kees Cook
2017-11-16 7:45 ` Kees Cook
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=20171120195027.GA20045@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=dave@nullcore.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.