From: Kees Cook <keescook@chromium•org>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: Dominik Czarnota <dominik.czarnota@trailofbits•com>,
stable <stable@vger•kernel.org>, Jessica Yu <jeyu@kernel•org>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Andrew Morton <akpm@linux-foundation•org>,
Alexei Starovoitov <ast@kernel•org>,
Daniel Borkmann <daniel@iogearbox•net>,
Martin KaFai Lau <kafai@fb•com>, Song Liu <songliubraving@fb•com>,
Yonghong Song <yhs@fb•com>, Andrii Nakryiko <andriin@fb•com>,
KP Singh <kpsingh@chromium•org>,
"Naveen N. Rao" <naveen.n.rao@linux•ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel•com>,
"David S. Miller" <davem@davemloft•net>,
Masami Hiramatsu <mhiramat@kernel•org>,
Jakub Kicinski <kuba@kernel•org>,
"Steven Rostedt (VMware)" <rostedt@goodmis•org>,
Dmitry Safonov <0x7f454c46@gmail•com>,
Will Deacon <will@kernel•org>,
Alexey Dobriyan <adobriyan@gmail•com>,
Marc Zyngier <maz@kernel•org>,
Masahiro Yamada <masahiroy@kernel•org>,
Al Viro <viro@zeniv•linux.org.uk>,
Matteo Croce <mcroce@redhat•com>,
Edward Cree <ecree@solarflare•com>,
Nicolas Dichtel <nicolas.dichtel@6wind•com>,
Thomas Richter <tmricht@linux•ibm.com>,
Ingo Molnar <mingo@kernel•org>, Netdev <netdev@vger•kernel.org>,
bpf <bpf@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH 4/5] kprobes: Do not expose probe addresses to non-CAP_SYSLOG
Date: Sun, 5 Jul 2020 13:19:27 -0700 [thread overview]
Message-ID: <202007051318.CA51091A@keescook> (raw)
In-Reply-To: <CAHk-=wgEkTsNRvEM9W_JiVN6t70SnPuP=-1=LyhLS_BJ25Q4sQ@mail.gmail.com>
On Sun, Jul 05, 2020 at 01:10:54PM -0700, Linus Torvalds wrote:
> On Fri, Jul 3, 2020 at 8:50 AM Kees Cook <keescook@chromium•org> wrote:
> >
> > With 67 kthreads on a booted system, this patch does not immediately
> > blow up...
>
> Did you try making read/write inc/dec that thing too? Or does that
> just blow up with tons of warnings?
I hadn't gotten to that yet. I need to catch up on other stuff first,
and I thought I'd give people time to scream if they tested this
themselves. :)
--
Kees Cook
next prev parent reply other threads:[~2020-07-05 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 23:26 [PATCH 0/5] Refactor kallsyms_show_value() users for correct cred Kees Cook
2020-07-02 23:26 ` [PATCH 1/5] kallsyms: Refactor kallsyms_show_value() to take cred Kees Cook
2020-07-02 23:26 ` [PATCH 2/5] module: Refactor section attr into bin attribute Kees Cook
2020-07-03 6:02 ` Greg Kroah-Hartman
2020-07-03 15:29 ` Kees Cook
2020-07-08 16:10 ` Jessica Yu
2020-07-02 23:26 ` [PATCH 3/5] module: Do not expose section addresses to non-CAP_SYSLOG Kees Cook
2020-07-08 16:12 ` Jessica Yu
2020-07-02 23:26 ` [PATCH 4/5] kprobes: Do not expose probe " Kees Cook
2020-07-03 1:00 ` Linus Torvalds
2020-07-03 15:13 ` Kees Cook
2020-07-03 15:50 ` Kees Cook
2020-07-05 20:10 ` Linus Torvalds
2020-07-05 20:19 ` Kees Cook [this message]
2020-07-10 14:09 ` Masami Hiramatsu
2020-07-02 23:26 ` [PATCH 5/5] bpf: Check correct cred for CAP_SYSLOG in bpf_dump_raw_ok() 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=202007051318.CA51091A@keescook \
--to=keescook@chromium$(echo .)org \
--cc=0x7f454c46@gmail$(echo .)com \
--cc=adobriyan@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=andriin@fb$(echo .)com \
--cc=anil.s.keshavamurthy@intel$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dominik.czarnota@trailofbits$(echo .)com \
--cc=ecree@solarflare$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jeyu@kernel$(echo .)org \
--cc=kafai@fb$(echo .)com \
--cc=kpsingh@chromium$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=masahiroy@kernel$(echo .)org \
--cc=maz@kernel$(echo .)org \
--cc=mcroce@redhat$(echo .)com \
--cc=mhiramat@kernel$(echo .)org \
--cc=mingo@kernel$(echo .)org \
--cc=naveen.n.rao@linux$(echo .)ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nicolas.dichtel@6wind$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=songliubraving@fb$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
--cc=tmricht@linux$(echo .)ibm.com \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=will@kernel$(echo .)org \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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