public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	efault@gmx.de, Arne Jansen <lists@die-jansens.de>
Subject: Re: [PATCH 3/3] printk: Avoid all wakeups from printk
Date: Thu, 09 Jun 2011 18:25:51 +0200	[thread overview]
Message-ID: <1307636751.3941.91.camel@twins> (raw)
In-Reply-To: <20110609155134.GA1681@elte.hu>

On Thu, 2011-06-09 at 17:51 +0200, Ingo Molnar wrote:
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > On Thu, Jun 9, 2011 at 7:23 AM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > > Subject: printk: Avoid all wakeups from printk
> > > From: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Date: Wed Jun 08 17:29:59 CEST 2011
> > 
> > Looks good to me.  Is it working? You said that some early version 
> > of this caused problems for Ingo?
> 
> Yeah, it locked up during lockup in the middle of a printk and i 
> bisected it back to the third (most dangerous) commit - will retry 
> this version if Peter thinks it's materially different.

Well, please try again, the patch isn't different, but your .config
didn't want to reproduce at all for me, so if you've got a machine that
reliably fails, we can have a poke at it.

      reply	other threads:[~2011-06-09 16:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 13:06 [PATCH 0/3] printk: Remove lockdep_off() and wakeups Peter Zijlstra
2011-06-09 13:06 ` [PATCH 1/3] printk: Release console_sem after logbuf_lock Peter Zijlstra
2011-06-09 20:06   ` Andrew Morton
2011-06-09 20:27     ` Ingo Molnar
2011-06-09 20:54       ` Peter Zijlstra
2011-06-09 21:07         ` Andrew Morton
2011-06-09 23:57           ` Hugh Dickins
2011-06-10  0:08             ` Andrew Morton
2011-06-10  9:33               ` Ingo Molnar
2011-06-10  9:40                 ` Peter Zijlstra
2011-06-10  9:42                   ` Peter Zijlstra
2011-06-10 11:28             ` Peter Zijlstra
2011-06-10 12:30               ` Peter Zijlstra
2011-06-10 12:34                 ` Ingo Molnar
2011-06-10 12:41                   ` Peter Zijlstra
2011-06-10 12:42                     ` Peter Zijlstra
2011-06-23 19:03                 ` Pavel Machek
2011-06-10  9:30         ` Ingo Molnar
2011-06-10 10:15   ` Peter Zijlstra
2011-06-09 13:06 ` [PATCH 2/3] printk, lockdep: Remove lockdep_off() usage Peter Zijlstra
2011-06-10 13:23   ` Peter Zijlstra
2011-06-09 13:06 ` [PATCH 3/3] printk: Avoid all wakeups from printk Peter Zijlstra
2011-06-09 13:32   ` Ingo Molnar
2011-06-09 13:40     ` Peter Zijlstra
2011-06-09 13:55       ` Ingo Molnar
2011-06-09 14:06         ` Peter Zijlstra
2011-06-09 14:19           ` Ingo Molnar
2011-06-09 14:23             ` Peter Zijlstra
2011-06-09 15:47               ` Linus Torvalds
2011-06-09 15:51                 ` Ingo Molnar
2011-06-09 16:25                   ` Peter Zijlstra [this message]

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=1307636751.3941.91.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@die-jansens.de \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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