From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sasha Levin <levinsasha928@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
"pmladek@suse.com" <pmladek@suse.com>,
"sergey.senozhatsky@gmail.com" <sergey.senozhatsky@gmail.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: sched: serial port lockdep warning when offlining CPUs
Date: Thu, 28 Sep 2017 21:15:21 +0900 [thread overview]
Message-ID: <20170928121521.GD687@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170928120722.ir5tcclsg336ou2n@hirez.programming.kicks-ass.net>
On (09/28/17 14:07), Peter Zijlstra wrote:
[..]
> > Nah.. WARN's _should_ not trigger. If they do we fix that.
> >
> > Getting a lockdep splat after a WARN is something I can live with.
> >
> > And you really don't want that deferred nonsense for WARNs, because that
> > means you'll risk not over getting the output.
>
> Note that I'm not likely to care too much either way, because I'm simply
> not using any of that printk() nonsense ;-)
>
>
> I'll repost my patches now; otherwise I'll forget again anyway.
#define printk printk_deferred
should also do the trick and... make the kernel great again! :)
-ss
next prev parent reply other threads:[~2017-09-28 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 9:19 Sasha Levin
2017-09-28 9:38 ` Peter Zijlstra
2017-09-28 10:30 ` Sergey Senozhatsky
2017-09-28 11:36 ` Sergey Senozhatsky
2017-09-28 11:45 ` Levin, Alexander (Sasha Levin)
2017-09-28 11:55 ` Sergey Senozhatsky
2017-09-28 12:05 ` Peter Zijlstra
2017-09-28 12:07 ` Peter Zijlstra
2017-09-28 12:15 ` Sergey Senozhatsky [this message]
2017-09-28 12:28 ` Peter Zijlstra
2017-09-28 11:47 ` Peter Zijlstra
2017-09-28 11:51 ` Sergey Senozhatsky
2017-09-28 11:04 ` Levin, Alexander (Sasha Levin)
2017-09-28 11:13 ` Sergey Senozhatsky
2017-09-28 11:38 ` Peter Zijlstra
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=20170928121521.GD687@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=alexander.levin@verizon.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®