From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Dmitry Vyukov <dvyukov@google.com>, Jiri Slaby <jslaby@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Garrett <mjg59@google.com>,
Andi Kleen <ak@linux.intel.com>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Add kernel config option for fuzz testing.
Date: Fri, 13 Mar 2020 09:31:07 +0100 [thread overview]
Message-ID: <20200313083107.GV12561@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200312182935.70ed6516@gandalf.local.home>
On Thu, Mar 12, 2020 at 06:29:35PM -0400, Steven Rostedt wrote:
> > @@ -705,10 +706,12 @@ static void lockdep_print_held_locks(struct task_struct *p)
> > * It's not reliable to print a task's held locks if it's not sleeping
> > * and it's not the current task.
> > */
> > - if (p->state == TASK_RUNNING && p != current)
> > - return;
> > + unreliable = p->state == TASK_RUNNING && p != current;
> > for (i = 0; i < depth; i++) {
> > - printk(" #%d: ", i);
> > + if (unreliable)
> > + printk(" #%d?: ", i);
> > + else
> > + printk(" #%d: ", i);
>
> Have you tried submitting this? Has Peter nacked it?
It has definite UaF potential... do we have a boot parameter that
signals the willingness to trade safetly for more debug output?
Over all, the risk of this going *bang* is quite low I think.
next prev parent reply other threads:[~2020-03-13 8:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 13:58 [PATCH v2] Add kernel config option for fuzz testing Tetsuo Handa
2020-03-07 16:28 ` Jiri Slaby
2020-03-08 6:52 ` Greg Kroah-Hartman
2020-03-08 16:13 ` Linus Torvalds
2020-03-09 11:22 ` Tetsuo Handa
2020-03-09 13:23 ` Steven Rostedt
2020-03-09 15:39 ` Jiri Slaby
2020-03-10 6:30 ` Dmitry Vyukov
2020-03-11 14:11 ` Steven Rostedt
2020-03-12 19:23 ` Dmitry Vyukov
2020-03-12 21:59 ` Tetsuo Handa
2020-03-12 22:29 ` Steven Rostedt
2020-03-13 8:31 ` Peter Zijlstra [this message]
2020-03-15 5:54 ` Dmitry Vyukov
2020-03-21 4:49 ` Tetsuo Handa
2020-03-24 10:37 ` Dmitry Vyukov
2020-03-26 11:10 ` Tetsuo Handa
2020-04-10 4:38 ` Tetsuo Handa
2020-03-08 6:52 ` Greg Kroah-Hartman
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=20200313083107.GV12561@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@google.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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