From: Simon Horman <horms@verge.net.au>
To: Alexander Egorenkov <egorenar-dev@posteo.net>
Cc: rmk@armlinux.org.uk, kexec@lists.infradead.org
Subject: Re: [PATCH v2 1/1] arm: do not copy magic 4 bytes of appended DTB in zImage
Date: Sat, 17 Apr 2021 09:21:17 +0200 [thread overview]
Message-ID: <20210417072115.GC2573@vergenet.net> (raw)
In-Reply-To: <20210412111805.31643-1-egorenar-dev@posteo.net>
On Mon, Apr 12, 2021 at 01:18:05PM +0200, Alexander Egorenkov wrote:
> If the passed zImage happens to have a DTB appended, then the magic 4 bytes
> of the DTB are copied together with the kernel image. This leads to
> failed kexec boots because the decompressor finds the aforementioned
> DTB magic and falsely tries to replace the DTB passed in the register r2
> with the non-existent appended one.
>
> Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
> ---
>
> v1 -> v2:
> * Add a comment explaining the reason for introducing kernel_buf_size
Thanks Alexander, applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2021-04-17 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 11:18 [PATCH v2 1/1] arm: do not copy magic 4 bytes of appended DTB in zImage Alexander Egorenkov
2021-04-17 7:21 ` Simon Horman [this message]
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=20210417072115.GC2573@vergenet.net \
--to=horms@verge.net.au \
--cc=egorenar-dev@posteo.net \
--cc=kexec@lists.infradead.org \
--cc=rmk@armlinux.org.uk \
/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