From: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Eric Biederman <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Dave Young <dyoung@redhat.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-ima-devel@lists.sourceforge.net,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Kexec regression in next-20160906
Date: Tue, 06 Sep 2016 20:33:20 -0300 [thread overview]
Message-ID: <2229914.bQjEFCIRgO@hactar> (raw)
In-Reply-To: <20160906220936.4txqzodkgknhjiyh@atomide.com>
Hello Tony,
Am Dienstag, 06 September 2016, 15:09:37 schrieb Tony Lindgren:
> Looks like commit 5c01cdd2d4bc ("kexec_file: allow skipping checksum
> calculation for some segments") makes next-20160916 stop working for
> me at least on ARM.
>
> I now get "kexec_load failed: Invalid argument error" on loading the
> new kernel to memory with kexec -l.
>
> Reverting the following two commits makes things work for me again:
>
> d2bf993afdf1 ("kexec_file: add mechanism to update kexec segments")
> 5c01cdd2d4bc ("kexec_file: allow skipping checksum calculation for
> some segments")
Thanks for reporting the problem and finding the commit that caused it.
The only thing in commit 5c01cdd2d4bc which can affect kexec_load is the
fact that struct kexec_segment has a new member.
This is probably breaking the ABI on ARM, then. I verified that kexec_load
kept working on ppc64le with a kexec binary compiled with the original
struct kexec_segment definition, but apparently I got lucky.
I'll prepare a new version of the kexec buffer hand-over series which
doesn't touch struct kexec_segment.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next parent reply other threads:[~2016-09-06 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160906220936.4txqzodkgknhjiyh@atomide.com>
2016-09-06 23:33 ` Thiago Jung Bauermann [this message]
2016-09-07 8:08 ` Kexec regression in next-20160906 Russell King - ARM Linux
2016-09-08 15:23 ` Thiago Jung Bauermann
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=2229914.bQjEFCIRgO@hactar \
--to=bauerman@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tony@atomide.com \
--cc=zohar@linux.vnet.ibm.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).