kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: ats-kumagai@wm.jp.nec.com, kexec@lists.infradead.org,
	thgarnie@google.com
Subject: Re: [PATCH 0/3] makedumpfile: Add support of mm randomization
Date: Thu, 22 Sep 2016 16:57:15 +0800	[thread overview]
Message-ID: <20160922085715.GA378@x1> (raw)
In-Reply-To: <20160922084848.GA18964@dhcp-128-65.nay.redhat.com>

On 09/22/16 at 04:48pm, Dave Young wrote:
> Fix email address of Atsushi Kumagai..
> 
> On 09/22/16 at 04:45pm, Dave Young wrote:
> > Hi, Baoquan
> > 
> > On 08/29/16 at 04:54pm, Baoquan He wrote:
> > > Hi Atsushi and Thomas,

Did you apply below kexec patch either?

kexec/arch/i386: Add support for KASLR memory randomization

Please search it in kexec mailing list, Thomas posted it.

> > > 
> > > This is a draft patchset. I just checked x86_64 implementation according to
> > > Thomas's mm randomization related patches. Not sure if this will affect
> > > other ARCH or XEN. Especially for patch 1/3 and patch 2/3, just a original
> > > idea. I tested on x86_64, passed.
> > > 
> > > And also kernel patch need be adjusted so that number_table.X of makedumpfile
> > > can be used. Will add comment to Thomas's kernel patch.
> > > 
> > > Baoquan He (3):
> > >   makedumpfile: Get info->kernel_version from SYMBOL(init_uts_ns)
> > >     earlier
> > >   makedumpfile: Move get_versiondep_info calling earlier
> > >   makedumpfile: Add support for MM randomization
> > > 
> > >  arch/x86_64.c  | 26 +++++++++-----------------
> > >  makedumpfile.c | 45 ++++++++++++++++++++++++++++++++++++---------
> > >  makedumpfile.h |  3 +++
> > >  3 files changed, 48 insertions(+), 26 deletions(-)
> > > 
> > 
> > With these patch applied, I still get a makedumpfile failure below in Fedora:
> > Kernel applied your patch to export the 3 symbols.
> > 
> > kdump: saving vmcore-dmesg.txt complete                                        
> > kdump: saving vmcore                                                           
> > kdump: saving vmcore failed                                                    
> > [FAILED] Failed to start Kdump Vmcore Save Service. 
> > 
> > Thanks
> > Dave

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2016-09-22  8:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29  8:54 [PATCH 0/3] makedumpfile: Add support of mm randomization Baoquan He
2016-08-29  8:54 ` [PATCH 1/3] makedumpfile: Get info->kernel_version from SYMBOL(init_uts_ns) earlier Baoquan He
2016-08-29  8:54 ` [PATCH 2/3] makedumpfile: Move get_versiondep_info calling earlier Baoquan He
2016-08-29  8:54 ` [PATCH 3/3] makedumpfile: Add support for MM randomization Baoquan He
2016-08-31  7:56   ` Atsushi Kumagai
2016-09-30  4:56     ` Baoquan He
2016-10-04  1:40       ` Atsushi Kumagai
2016-10-04 13:09         ` Baoquan He
2016-08-29  9:03 ` [PATCH 0/3] makedumpfile: Add support of mm randomization Baoquan He
2016-09-22  8:45 ` Dave Young
2016-09-22  8:48   ` Dave Young
2016-09-22  8:57     ` Baoquan He [this message]
2016-09-22  9:03       ` Dave Young
2016-09-22  9:07         ` Baoquan He
2016-09-23  2:38           ` Dave Young

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=20160922085715.GA378@x1 \
    --to=bhe@redhat.com \
    --cc=ats-kumagai@wm.jp.nec.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=thgarnie@google.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).