From: Andrew Morton <akpm@linux-foundation.org>
To: Minfei Huang <mnfhuang@gmail.com>
Cc: ebiederm@xmission.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, mhuang@redhat.com
Subject: Re: [PATCH V2 1/2] kexec: Make a pair of map/unmap reserved pages in error path
Date: Tue, 1 Mar 2016 13:56:58 -0800 [thread overview]
Message-ID: <20160301135658.341928989a18949d97998abd@linux-foundation.org> (raw)
In-Reply-To: <1456819349-8650-2-git-send-email-mnfhuang@gmail.com>
On Tue, 1 Mar 2016 16:02:28 +0800 Minfei Huang <mnfhuang@gmail.com> wrote:
> For some arch, kexec shall map the reserved pages, then use them, when
> we try to start the kdump service.
Which architectures are these, by the way?
> kexec may return directly, without unmaping the reserved pages, if it
> fails during starting service. To fix it, we make a pair of map/unmap
> reserved pages both in generic path and error path.
I'm having trouble understanding the urgency of this patch. Do you
think it is needed in 4.5? -stable? If so, why?
Thanks.
next prev parent reply other threads:[~2016-03-01 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 8:02 [PATCH V2 0/2] " Minfei Huang
2016-03-01 8:02 ` [PATCH V2 1/2] " Minfei Huang
2016-03-01 21:56 ` Andrew Morton [this message]
2016-03-02 3:03 ` Minfei Huang
2016-03-01 8:02 ` [PATCH V2 2/2] kexec: Do a cleanup for function kexec_load Minfei Huang
2016-03-01 22:05 ` Andrew Morton
2016-03-01 9:53 ` [PATCH V2 0/2] kexec: Make a pair of map/unmap reserved pages in error path Xunlei Pang
2016-03-23 2:48 ` Baoquan He
2016-03-23 3:32 ` Xunlei Pang
2016-03-23 8:23 ` Baoquan He
2016-03-23 9:59 ` Xunlei Pang
2016-03-23 12:32 ` Baoquan He
2016-03-24 8:36 ` Xunlei Pang
2016-03-26 15:17 ` Minfei Huang
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=20160301135658.341928989a18949d97998abd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhuang@redhat.com \
--cc=mnfhuang@gmail.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
all inboxes | Powered by JetHome®