linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrea della Porta <andrea.porta@suse.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: nik.borisov@suse.com, arnd@arndb.de, mark.rutland@arm.com,
	Andrea della Porta <andrea.porta@suse.com>
Subject: [PATCH v2 0/4] arm64: Make Aarch32 compatibility enablement optional at boot
Date: Mon, 23 Oct 2023 16:42:19 +0200	[thread overview]
Message-ID: <cover.1698069331.git.andrea.porta@suse.com> (raw)

This is the second attempt of the patch, reviewed as follows:

* Reworked subject and description to avoid the term 'emulation' and to
  address generically 'exceptions' instead of 'syscalls' (mark.rutland)

* Moved aarch32_enabled() check inside system_supports_32bit_el0()
  (mark.rutland)

* Renamed AARCH32_EMULATION_DEFAULT_DISABLED to AARCH32_SUPPORT_DEFAULT_DISABLED
  (mark.rutland)

* Fixed a compilation Warning about missing function prototype
  Closes: https://lore.kernel.org/oe-kbuild-all/202310230423.r2U4Lqr8-lkp@intel.com/

This is just for completeness since other possible solutions have been
proposed that could be better suited, see for example:
https://lkml.kernel.org/linux-fsdevel/20210916131816.8841-1-will@kernel.org/
and followups. So, this patchset is just for reference, may be useful in the
future if some kind of exploit is found to bypass the 32bit process
enablement check (letting a process call 32bit syscalls) and nothing better
has been proposed meanwhile.

Andrea della Porta (4):
  arm64: Introduce aarch32_enabled()
  arm64/process: Make loading of 32bit processes depend on
    aarch32_enabled()
  arm64/entry-common: Make Aarch32 exceptions' availability depend on
    aarch32_enabled()
  arm64: Make Aarch32 support boot time configurable

 .../admin-guide/kernel-parameters.txt         |  7 ++++
 arch/arm64/Kconfig                            |  9 +++++
 arch/arm64/include/asm/cpufeature.h           | 20 +++++++++--
 arch/arm64/include/asm/exception.h            |  7 ++++
 arch/arm64/kernel/entry-common.c              | 33 +++++++++++++++++--
 5 files changed, 71 insertions(+), 5 deletions(-)

-- 
2.35.3


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-10-23 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 14:42 Andrea della Porta [this message]
2023-10-23 14:42 ` [PATCH v2 1/4] arm64: Introduce aarch32_enabled() Andrea della Porta
2023-10-24 11:56   ` Robin Murphy
2023-11-15 15:36     ` Andrea della Porta
2023-10-23 14:42 ` [PATCH v2 2/4] arm64/process: Make loading of 32bit processes depend on aarch32_enabled() Andrea della Porta
2023-10-23 14:42 ` [PATCH v2 3/4] arm64/entry-common: Make Aarch32 exceptions' availability " Andrea della Porta
2023-10-25 11:27   ` Mark Rutland
2023-11-15 16:09     ` Andrea della Porta
2023-10-23 14:42 ` [PATCH v2 4/4] arm64: Make Aarch32 support boot time configurable Andrea della Porta

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=cover.1698069331.git.andrea.porta@suse.com \
    --to=andrea.porta@suse.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nik.borisov@suse.com \
    --cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).