public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	akinobu.mita@gmail.com, jack@suse.cz,
	sergey.senozhatsky.work@gmail.com, peter@hurleysoftware.com,
	torvalds@linux-foundation.org
Subject: Re: [PATCH v5] lib/spinlock_debug.c: prevent a recursive cycle in the debug code
Date: Tue, 2 Feb 2016 11:34:36 +0900	[thread overview]
Message-ID: <20160202023436.GG29804@X58A-UD3R> (raw)
In-Reply-To: <20160130092743.GA13745@gmail.com>

On Sat, Jan 30, 2016 at 10:27:43AM +0100, Ingo Molnar wrote:
> 
> * Byungchul Park <byungchul.park@lge.com> wrote:
> 
> > +
> > +	/*
> > +	 * If this function is called from printk(), then we should
> > +	 * not call printk() more. Or it will cause an infinite
> > +	 * recursive cycle!
> 
> This should be something like:
> 
> > +	 * If this function is called from within printk() then we
> > +	 * should not call printk() again, or it will recurse
> > +	*  infinitely.
> 
> Thanks,

Thank you very much. Not easy to me.

> 
> 	Ingo

  reply	other threads:[~2016-02-02  2:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 12:43 [PATCH v5] lib/spinlock_debug.c: prevent a recursive cycle in the debug code Byungchul Park
2016-01-29 12:54 ` Byungchul Park
2016-01-31 12:40   ` Sergey Senozhatsky
2016-02-01  1:45     ` Byungchul Park
2016-02-01  2:13       ` Sergey Senozhatsky
2016-01-30  9:27 ` Ingo Molnar
2016-02-02  2:34   ` Byungchul Park [this message]
2016-02-01  2:31 ` Sergey Senozhatsky
2016-02-01  6:28   ` Byungchul Park

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=20160202023436.GG29804@X58A-UD3R \
    --to=byungchul.park@lge.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=sergey.senozhatsky.work@gmail.com \
    --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