From: Matthew Garrett <mjg59@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [Linux 5.2.x] /sys/kernel/debug/tracing/events/power/cpu_idle/id: BUG: kernel NULL pointer dereference, address: 0000000000000000
Date: Mon, 12 Aug 2019 09:24:30 -0700 [thread overview]
Message-ID: <CACdnJusGKAx-APuDi2+hqSSVXeeH5hBq4Chi-rPirDos4MvhgQ@mail.gmail.com> (raw)
In-Reply-To: <20190812112853.53ecc122@gandalf.local.home>
On Mon, Aug 12, 2019 at 8:29 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> From what I understand, Matthew's "lockdown" work is to prevent the
> system from doing anything to see what is happening in the kernel. This
> includes tracefs. This looks like it is working as designed.
Oopsing the kernel isn't working as designed. Ben has a patch to fix this.
prev parent reply other threads:[~2019-08-12 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4b54ff1e-f18b-3c58-7caa-945a0775c24c@molgen.mpg.de>
[not found] ` <alpine.DEB.2.21.1908101910280.7324@nanos.tec.linutronix.de>
[not found] ` <01c7bc6b-dc6d-5eca-401a-8869e02f7c2a@molgen.mpg.de>
2019-08-10 21:11 ` [Linux 5.2.x] /sys/kernel/debug/tracing/events/power/cpu_idle/id: BUG: kernel NULL pointer dereference, address: 0000000000000000 Paul Menzel
2019-08-11 6:22 ` Thomas Gleixner
2019-08-11 9:46 ` Salvatore Bonaccorso
2019-08-11 12:58 ` Thomas Gleixner
2019-08-11 15:33 ` Salvatore Bonaccorso
2019-08-12 15:28 ` Steven Rostedt
2019-08-12 16:24 ` Matthew Garrett [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=CACdnJusGKAx-APuDi2+hqSSVXeeH5hBq4Chi-rPirDos4MvhgQ@mail.gmail.com \
--to=mjg59@google.com \
--cc=carnil@debian.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).