From: Don Zickus <dzickus@redhat.com>
To: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Gleb Natapov <gleb@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org, stable@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
Ingo Molnar <mingo@redhat.com>,
Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
yrl.pp-manager.tt@hitachi.com,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Thomas Gleixner <tglx@linutronix.de>,
Seiji Aguchi <seiji.aguchi@hds.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Re: [PATCH] [BUGFIX] crash/ioapic: Prevent crash_kexec() from deadlocking of ioapic_lock
Date: Thu, 22 Aug 2013 09:11:37 -0400 [thread overview]
Message-ID: <20130822131137.GL5564@redhat.com> (raw)
In-Reply-To: <5215CDEF.30004@hitachi.com>
On Thu, Aug 22, 2013 at 05:38:07PM +0900, Yoshihiro YUNOMAE wrote:
> >So, I agree with Eric, let's remove the disable_IO_APIC() stuff and keep
> >the code simpler.
>
> Thank you for commenting about my patch.
> I didn't know you already have submitted the patches for this deadlock
> problem.
>
> I can't answer definitively right now that no problems are induced by
> removing disable_IO_APIC(). However, my patch should be work well (and
> has already been merged to -tip tree). So how about taking my patch at
> first, and then discussing the removal of disabled_IO_APIC()?
It doesn't matter to me. My orignal patch last year was similar to yours
until it was suggested that we were working around a problem which was we
shouldn't touch the IO_APIC code on panic. Then I wrote the removal of
disable_IO_APIC patch and did lots of testing on it. I don't think I have
seen any issues with it (just the removal of disabling the lapic stuff).
Regardless, your patch fixes a similar problem we saw on RHEL, so I am
happy either way. The removal of the disable_IO_APIC() just makes the
code look cleaner.
Cheers,
Don
next prev parent reply other threads:[~2013-08-22 13:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 8:12 [PATCH] [BUGFIX] crash/ioapic: Prevent crash_kexec() from deadlocking of ioapic_lock Yoshihiro YUNOMAE
2013-08-19 9:46 ` Ingo Molnar
2013-08-20 0:06 ` Yoshihiro YUNOMAE
2013-08-20 10:12 ` Eric W. Biederman
2013-08-20 14:27 ` Don Zickus
2013-08-22 8:38 ` Yoshihiro YUNOMAE
2013-08-22 13:11 ` Don Zickus [this message]
2013-08-27 3:41 ` Yoshihiro YUNOMAE
2013-08-27 13:33 ` Don Zickus
2013-08-31 0:58 ` Eric W. Biederman
2013-09-02 3:09 ` Yoshihiro YUNOMAE
2013-09-03 0:12 ` Eric W. Biederman
2013-09-03 11:02 ` Yoshihiro YUNOMAE
2013-09-03 12:44 ` Eric W. Biederman
2013-09-04 9:40 ` Yoshihiro YUNOMAE
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=20130822131137.GL5564@redhat.com \
--to=dzickus@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gleb@redhat.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=sebastian@breakpoint.cc \
--cc=seiji.aguchi@hds.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yoshihiro.yunomae.ez@hitachi.com \
--cc=yrl.pp-manager.tt@hitachi.com \
--cc=zhangyanfei@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).