From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, Will Deacon <will@kernel.org>,
cki-project@redhat.com, xiawu@redhat.com, bhe@redhat.com,
linux-arm-kernel@lists.infradead.org, james.morse@arm.com
Subject: Re: [PATCH] arm64: avoid executing padding bytes during kexec / hibernation (WAS: Re: ? FAIL (91/181 SKIPPED): Test report for for-kernelci (6.2.0-rc5, arm-next, 2e84eedb))
Date: Fri, 27 Jan 2023 17:46:55 +0000 [thread overview]
Message-ID: <Y9QOD7qJ6ZYL0cY+@arm.com> (raw)
In-Reply-To: <Y9PAEl0VPwIrQOnB@FVFF77S0Q05N>
On Fri, Jan 27, 2023 at 12:14:10PM +0000, Mark Rutland wrote:
> From 8c82c71d810be311f10703b91563a301e56be910 Mon Sep 17 00:00:00 2001
> From: Mark Rutland <mark.rutland@arm.com>
> Date: Fri, 27 Jan 2023 11:08:20 +0000
> Subject: [PATCH] arm64: avoid executing padding bytes during kexec /
> hibernation
>
> Currently we rely on the HIBERNATE_TEXT section starting with the entry
> point to swsusp_arch_suspend_exit, and the KEXEC_TEXT section starting
> with the entry point to arm64_relocate_new_kernel. In both cases we copy
> the entire section into a dynamically-allocated page, and then later
> branch to the start of this page.
Queued on top of the arm64 for-next/ftrace branch. Thanks.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-27 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 9:21 ❌ FAIL (91/181 SKIPPED): Test report for for-kernelci (6.2.0-rc5, arm-next, 2e84eedb) cki-project
2023-01-26 12:52 ` Will Deacon
2023-01-26 14:53 ` ? " Mark Rutland
2023-01-26 15:09 ` Mark Rutland
2023-01-26 15:17 ` Will Deacon
2023-01-26 17:25 ` Mark Rutland
2023-01-26 18:33 ` Ard Biesheuvel
2023-01-27 12:14 ` [PATCH] arm64: avoid executing padding bytes during kexec / hibernation (WAS: Re: ? FAIL (91/181 SKIPPED): Test report for for-kernelci (6.2.0-rc5, arm-next, 2e84eedb)) Mark Rutland
2023-01-27 12:45 ` Ard Biesheuvel
2023-01-27 17:46 ` Catalin Marinas [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=Y9QOD7qJ6ZYL0cY+@arm.com \
--to=catalin.marinas@arm.com \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=cki-project@redhat.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=xiawu@redhat.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).