linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Juerg Haefliger <juerg.haefliger@canonical.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	mingo@kernel.org, tglx@linutronix.de, peterz@infradead.org,
	dave.hansen@linux.intel.com, hughd@google.com, luto@kernel.org
Subject: Re: KAISER: kexec triggers a warning
Date: Mon, 4 Dec 2017 09:52:54 +0800	[thread overview]
Message-ID: <20171204015254.GG15074@x1> (raw)
In-Reply-To: <20171201152710.z2nushke5paoqhxc@pd.tnic>

On 12/01/17 at 04:27pm, Borislav Petkov wrote:
> On Fri, Dec 01, 2017 at 11:18:51PM +0800, Baoquan He wrote:
> > On 12/01/17 at 02:52pm, Juerg Haefliger wrote:
> > > Loading a kexec kernel using today's linux-tip master with KAISER=y
> > > triggers the following warning:
> > 
> > I also noticed this when trigger a crash to jump to kdump kernel, and
> > kdump kernel failed to bootup. I am trying to fix it on tip/WIP.x86/mm.
> > Maybe still need a little time.
> 
> Save yourself the energy, the WARN is wrong there and wil go away.

OK, will test patch.

> -- 
> 
> Good mailing practices for 400: avoid top-posting and trim the reply.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-12-04  1:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 13:52 Juerg Haefliger
2017-12-01 15:18 ` Baoquan He
2017-12-01 15:27   ` Borislav Petkov
2017-12-04  1:52     ` Baoquan He [this message]
2017-12-01 15:31 ` Dave Hansen
2017-12-01 15:37   ` Borislav Petkov
2017-12-01 16:38     ` Eduardo Valentin
2017-12-01 17:03       ` Borislav Petkov

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=20171204015254.GG15074@x1 \
    --to=bhe@redhat.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hughd@google.com \
    --cc=juerg.haefliger@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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