public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Make kexec work with CONFIG_DEBUG_RODATA enabled
Date: Wed, 30 Apr 2014 14:02:42 +0100	[thread overview]
Message-ID: <20140430130241.GA15719@arm.com> (raw)
In-Reply-To: <1398677507-6687-1-git-send-email-Nikolay.Borisov@arm.com>

Hi Nikolay,

On Mon, Apr 28, 2014 at 10:31:44AM +0100, Nikolay Borisov wrote:
> This patch makes kexec work on a kernel that has its .text section set to read
> only. The main reason of doing it is because there is a patch in the making 
> (http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/244779.html)
> which aims to make it possible to flag the kernel's code section as read-only,
> rendering kexec inoperable.
> 
> The first patch does the actual functional changes while the 2nd one is
> optional and is only to be used in case you have already applied the aforementioned
> CONFIG_DEBUG_RODATA patch
> 
> Patch 3 is also optional and tries to make the assembly code a bit more "sane"
> by introducing a .struct to describe the parameters for the kernel relocation
> stub. 
> 
> Those patches have been tested on linux 3.14 on THUMB-2/non-THUMB-2 host
> kernels. 
> 
> Patch 1 and 3 apply cleanly on 3.15-rc3 and Patch 2 applies cleanly, provided
> that Kees' patch is applied as well. 
> 
> Kees also managed to test that on a QEMU 2.0 based machine. 

Wouldn't it be far simpler to set_kernel_text_rw() on a kexec? At this
point, we've committed to replacing our image, so whether we can write to
the .text of the old image before we clobber it entirely seems somewhat
moot to me.

Will

  parent reply	other threads:[~2014-04-30 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  9:31 [PATCH 0/3] Make kexec work with CONFIG_DEBUG_RODATA enabled Nikolay Borisov
2014-04-28  9:31 ` [PATCH 1/3] ARM: kexec: Make kexec work with read-only kernel .text section Nikolay Borisov
2014-04-28  9:31 ` [PATCH 2/3] ARM: Kconfig: remove dependence of CONFIG_DEBUG_RODATA on !kexec Nikolay Borisov
2014-04-28  9:31 ` [PATCH 3/3] ARM: kexec: Use .struct to describe relocate_new_kernel parameter layout Nikolay Borisov
2014-04-30 13:02 ` Will Deacon [this message]
2014-04-30 13:19   ` [PATCH 0/3] Make kexec work with CONFIG_DEBUG_RODATA enabled Nikolay Borisov
2014-04-30 17:54     ` Kees Cook

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=20140430130241.GA15719@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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