[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20151008135611.1f8deadff8690df168daaedc@linux-foundation.org>
Date: Thu, 8 Oct 2015 13:56:11 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
Cc: Jan Kara <jack@...e.cz>,
HATAYAMA Daisuke <d.hatayama@...fujitsu.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Jiri Kosina <jkosina@...e.cz>, Baoquan He <bhe@...hat.com>,
Prarit Bhargava <prarit@...hat.com>,
Xie XiuQi <xiexiuqi@...wei.com>,
Seth Jennings <sjenning@...hat.com>,
linux-kernel@...r.kernel.org,
"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: Re: [PATCH] panic: release stale console lock to always get the
logbuf printed out
On Thu, 08 Oct 2015 12:03:25 +0200 Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
> > If we picked up patch "kernel: Avoid softlockups in
> > stop_machine() during heavy printing" from my series (it's completely
> > independent, I've attached the latest version), the result would look less
> > hacky to me (attached). Thoughts?
>
> Haven't tested it but should also work...
Well, I expect we'll be merging Jan's lockup-avoidance code fairly
soon. There's no point in solving the same problem twice.
Sp please, do take a closer look at the proposed patches and if
possible, runtime test them?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists