From: Steven Rostedt <rostedt@goodmis.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: 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, Matthew Garrett <mjg59@google.com>
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 11:28:53 -0400 [thread overview]
Message-ID: <20190812112853.53ecc122@gandalf.local.home> (raw)
In-Reply-To: <20190811153326.GA8036@eldamar.local>
On Sun, 11 Aug 2019 17:33:26 +0200
Salvatore Bonaccorso <carnil@debian.org> wrote:
> Thomas,
>
> On Sun, Aug 11, 2019 at 02:58:15PM +0200, Thomas Gleixner wrote:
> > Salvatore,
> >
> > On Sun, 11 Aug 2019, Salvatore Bonaccorso wrote:
> > > On Sun, Aug 11, 2019 at 08:22:35AM +0200, Thomas Gleixner wrote:
> > > > On Sat, 10 Aug 2019, Paul Menzel wrote:
> > > > > For the record. It is also reproducible with Linux 5.2.6, and trying to print
> > > > > the file contents with cat already fails.
> > > > >
> > > > > ```
> > > > > $ sudo ls -l /sys/kernel/debug/tracing/events/power/cpu_idle/id
> > > > > -r--r--r-- 1 root root 0 Aug 10 23:05
> > > > > /sys/kernel/debug/tracing/events/power/cpu_idle/id
> > > > > $ sudo cat /sys/kernel/debug/tracing/events/power/cpu_idle/id
> > > > > Killed
> > > > > ```
> > >
> > > This seems to be related to https://bugs.debian.org/934304 (in
> > > particular https://bugs.debian.org/934304#29). The mentioned patch
> > > features/all/lockdown/0031-tracefs-Restrict-tracefs-when-the-kernel-is-locked-d.patch
> > > is a backport of https://patchwork.kernel.org/patch/11069661/ with
> > > only change that it is converted back to the non-LSM lockdown API.
> >
> > So that's a debian kernel specific issue?
>
> "yes". A kernel build without the above patch does not exhibit the
> issue. So the issue is specific to that lockdown patch ("tracefs:
> Restrict tracefs when the kernel is locked down").
>
> Steven and Matthew are both CC'ed.
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.
Perhaps it's something in debian setup that needs to keep tracefs from
being selected as "lockdown", otherwise anything that tries to access
it, will have these issues.
-- Steve
next prev parent reply other threads:[~2019-08-12 15:28 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 [this message]
2019-08-12 16:24 ` Matthew Garrett
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=20190812112853.53ecc122@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=mjg59@google.com \
--cc=pmenzel@molgen.mpg.de \
--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).