mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <peterz@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: lockdep splat during suspend
Date: Thu, 17 Nov 2016 17:31:55 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1611171729320.3645@nanos> (raw)
In-Reply-To: <20161117162943.ul2gldjt6qhz35dz@linutronix.de>

On Thu, 17 Nov 2016, Sebastian Andrzej Siewior wrote:

> On 2016-11-17 13:43:58 [+0100], Borislav Petkov wrote:
> > Hi dudes,
> Hi Boris,
> 
> > this is what I'm seeing on 4.9-rc5+tip/master during suspend. (And yes,
> > that printk thing is nuts):
> 
> assuming this happens always, could you please try to revert
>   90b14889d2f9 ("kernel/printk: Convert to hotplug state machine")
> and see if it still there? I am curious if this is new or old splat.

It's a new one and that patch simply missed the fact, that the actions in
the original notifier were all w/o FROZEN, but the conversion dropped
that. Which probably explains the splat because suspend/resume is where the
FROZEN stuff happens.

Boris, does the patch below fix the issue for you ?

Thanks,

	tglx

8<-----------------------

--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2194,8 +2194,10 @@ void resume_console(void)
  */
 static int console_cpu_notify(unsigned int cpu)
 {
-	console_lock();
-	console_unlock();
+	if (!cpuhp_tasks_frozen) {
+		console_lock();
+		console_unlock();
+	}
 	return 0;
 }
 

  reply	other threads:[~2016-11-17 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 12:43 Borislav Petkov
2016-11-17 16:29 ` Sebastian Andrzej Siewior
2016-11-17 16:31   ` Thomas Gleixner [this message]
2016-11-17 17:04     ` Borislav Petkov
2016-11-17 18:51     ` [tip:smp/hotplug] kernel/printk: Block cpuhotplug callback when tasks are frozen tip-bot for Thomas Gleixner

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=alpine.DEB.2.20.1611171729320.3645@nanos \
    --to=tglx@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®