All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	Kyle McMartin <kyle@kernel.org>,
	Dave Jones <davej@codemonkey.org.uk>, Jan Kara <jack@suse.com>,
	Calvin Owens <calvinowens@fb.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	kernel test robot <ying.huang@linux.intel.com>,
	kernel-team@fb.com,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] printk: clear console_may_schedule on panic flushing
Date: Mon, 11 Jan 2016 17:25:02 -0500	[thread overview]
Message-ID: <20160111222502.GM1898@mtj.duckdns.org> (raw)
In-Reply-To: <20160111220927.GL1898@mtj.duckdns.org>

Hello, again.

On Mon, Jan 11, 2016 at 05:09:27PM -0500, Tejun Heo wrote:
> > You didn't comment on Sergey's observations
> > (https://lkml.org/lkml/2015/12/2/1192), but I'm believing this is
> > a separate issue and that this patch is still good.
> 
> Missed that one somehow.  Will respond.

So, I agree with Jan's response there.  My patch wasn't a full
solution to the whole problem.  It solves a specific case (hang during
registration of a slow console device) and is also needed for future
improvements but we still need Jan's patchset and more to actually get
the problem solved.

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: lkp@lists.01.org
Subject: Re: [PATCH] printk: clear console_may_schedule on panic flushing
Date: Mon, 11 Jan 2016 17:25:02 -0500	[thread overview]
Message-ID: <20160111222502.GM1898@mtj.duckdns.org> (raw)
In-Reply-To: <20160111220927.GL1898@mtj.duckdns.org>

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

Hello, again.

On Mon, Jan 11, 2016 at 05:09:27PM -0500, Tejun Heo wrote:
> > You didn't comment on Sergey's observations
> > (https://lkml.org/lkml/2015/12/2/1192), but I'm believing this is
> > a separate issue and that this patch is still good.
> 
> Missed that one somehow.  Will respond.

So, I agree with Jan's response there.  My patch wasn't a full
solution to the whole problem.  It solves a specific case (hang during
registration of a slow console device) and is also needed for future
improvements but we still need Jan's patchset and more to actually get
the problem solved.

Thanks.

-- 
tejun

  reply	other threads:[~2016-01-11 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11  3:08 [lkp] [printk] db43e77a44: BUG: sleeping function called from invalid context at kernel/printk/printk.c:2328 kernel test robot
2016-01-11  3:08 ` kernel test robot
2016-01-11 18:43 ` [PATCH] printk: clear console_may_schedule on panic flushing Tejun Heo
2016-01-11 18:43   ` Tejun Heo
2016-01-11 21:59   ` Andrew Morton
2016-01-11 21:59     ` Andrew Morton
2016-01-11 22:09     ` Tejun Heo
2016-01-11 22:09       ` Tejun Heo
2016-01-11 22:25       ` Tejun Heo [this message]
2016-01-11 22:25         ` Tejun Heo
2016-01-12 13:50     ` Sergey Senozhatsky
2016-01-12 13:50       ` Sergey Senozhatsky

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=20160111222502.GM1898@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=calvinowens@fb.com \
    --cc=davej@codemonkey.org.uk \
    --cc=jack@suse.com \
    --cc=kernel-team@fb.com \
    --cc=kyle@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=ying.huang@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.