From: Andrew Morton <akpm@linux-foundation.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Jiri Kosina <jkosina@suse.cz>, Baoquan He <bhe@redhat.com>,
Prarit Bhargava <prarit@redhat.com>,
Xie XiuQi <xiexiuqi@huawei.com>,
Seth Jennings <sjenning@redhat.com>,
linux-kernel@vger.kernel.org,
"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [PATCH] panic: release stale console lock to always get the logbuf printed out
Date: Thu, 8 Oct 2015 13:56:11 -0700 [thread overview]
Message-ID: <20151008135611.1f8deadff8690df168daaedc@linux-foundation.org> (raw)
In-Reply-To: <87612hfziq.fsf@vitty.brq.redhat.com>
On Thu, 08 Oct 2015 12:03:25 +0200 Vitaly Kuznetsov <vkuznets@redhat.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?
next prev parent reply other threads:[~2015-10-08 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 17:02 Vitaly Kuznetsov
2015-10-07 22:34 ` Andrew Morton
2015-10-08 9:01 ` Jan Kara
2015-10-08 10:03 ` Vitaly Kuznetsov
2015-10-08 20:56 ` Andrew Morton [this message]
2015-10-09 10:10 ` Vitaly Kuznetsov
2015-10-09 12:44 ` Vitaly Kuznetsov
2015-10-12 3:02 ` kbuild test robot
2015-10-08 9:51 ` Vitaly Kuznetsov
2015-10-08 20:54 ` Andrew Morton
2015-10-09 10:09 ` Vitaly Kuznetsov
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=20151008135611.1f8deadff8690df168daaedc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=jack@suse.cz \
--cc=jkosina@suse.cz \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=prarit@redhat.com \
--cc=sjenning@redhat.com \
--cc=vkuznets@redhat.com \
--cc=xiexiuqi@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome