From: Baoquan He <bhe@redhat.com>
To: Petr Tesarik <ptesarik@suse.com>
Cc: Atsushi Kumagai <ats-kumagai@wm.jp.nec.com>, kexec@lists.infradead.org
Subject: Re: [makedumpfile PATCH 0/2] Fix calculations in exclude_segment()
Date: Tue, 23 Jan 2018 14:28:13 +0800 [thread overview]
Message-ID: <20180123062813.GB1968@localhost.localdomain> (raw)
In-Reply-To: <cover.1516354241.git.ptesarik@suse.com>
On 01/19/18 at 12:45pm, Petr Tesarik wrote:
> I have observed that makedumpfile --mem-usage shows bogus numbers
> on a kaslr-enabled kernel. This boils down to incorrect calculations
> in exclude_segment(). Consequently, data beyond a split LOAD segment
> are read from the wrong file offset.
>
> Petr Tesarik (2):
> Fix off-by-one errors in exclude_segment()
> Fix physical-to-virtual conversion in exclude_segment()
>
> elf_info.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
Ack the series, thanks!
>
> --
> 2.13.6
>
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-01-23 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 11:45 [makedumpfile PATCH 0/2] Fix calculations in exclude_segment() Petr Tesarik
2018-01-19 11:45 ` [makedumpfile PATCH 1/2] Fix off-by-one errors " Petr Tesarik
2018-01-22 8:20 ` Baoquan He
2018-01-19 11:45 ` [makedumpfile PATCH 2/2] Fix physical-to-virtual conversion " Petr Tesarik
2018-01-22 6:28 ` [makedumpfile PATCH 0/2] Fix calculations " Bhupesh Sharma
2018-01-23 6:28 ` Baoquan He [this message]
2018-01-23 8:49 ` Atsushi Kumagai
2018-01-25 9:15 ` Petr Tesarik
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=20180123062813.GB1968@localhost.localdomain \
--to=bhe@redhat.com \
--cc=ats-kumagai@wm.jp.nec.com \
--cc=kexec@lists.infradead.org \
--cc=ptesarik@suse.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).