From: Steven Rostedt <rostedt@goodmis.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Rik van Riel <riel@fb.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH] lockdep: Avoid triggering hardlockup from debug_show_all_locks()
Date: Tue, 23 Jan 2018 21:54:38 -0500 [thread overview]
Message-ID: <20180123215438.0257fa3e@vmware.local.home> (raw)
In-Reply-To: <20180124024955.GB651@jagdpanzerIV>
On Wed, 24 Jan 2018 11:49:55 +0900
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> wrote:
> Another problem, and I mentioned it somewhere in another email, is that
> upstream printk people don't receive enough [if any at all] feedback from
> guys who face printk issues. That's why every time printk_kthread re-surfaces
> the reaction is "this is not a real problem, no one is seeing printk issues
> like these, you idiot!". It'd be great to have more "we need ABC, because of
> XYZ, but printk crashes the system. Here is the backtrace, fix it" reports.
> As of now, those things mostly are not reported, that's why people are not
> convinced. Just my 5 cents.
If you are seeing these issues, have whoever is reporting them to Cc
LKML, and those of us that would care to listen.
-- Steve
next prev parent reply other threads:[~2018-01-24 2:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 22:00 [PATCH] lockdep: Avoid triggering hardlockup from debug_show_all_locks() Tejun Heo
2018-01-23 19:03 ` Rik van Riel
2018-01-23 20:57 ` Tejun Heo
2018-01-23 21:00 ` Steven Rostedt
2018-01-23 21:11 ` Tejun Heo
2018-01-24 2:49 ` Sergey Senozhatsky
2018-01-24 2:54 ` Steven Rostedt [this message]
2018-01-24 5:00 ` Sergey Senozhatsky
2018-01-24 19:10 ` Tejun Heo
2018-01-24 10:38 ` [tip:locking/urgent] locking/lockdep: " tip-bot for Tejun Heo
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=20180123215438.0257fa3e@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=riel@fb.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@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