Skip to content

x86: don't default to executable mappings

Jan Beulich xen-devel 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest4 patches 9 repliesIn review
  2. v14 patches 14 repliesSuperseded

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4x86: move syscall trampolines off the stackxen/arch/x86/setup.c xen/arch/x86/smpboot.c xen/arch/x86/x86_64/compat/entry.S +7 more+348 -1286 replies
2/4x86emul: move stubs off the stacktools/tests/x86_emulator/x86_emulate.c xen/arch/x86/x86_emulate.c xen/arch/x86/x86_emulate/x86_emulate.c +1 more+136 -301 reply
3/4x86: move I/O emulation stubs off the stackxen/arch/x86/traps.c+22 -81 reply
4/4x86: switch default mapping attributes to non-executablexen/arch/x86/domain.c xen/arch/x86/domain_page.c xen/arch/x86/mm.c +5 more+120 -281 reply

Reviews trailers per patch

All 4 patches have a Reviewed-by or Acked-by.

PatchAndrew Cooper
1/4R-b
2/4R-b
3/4R-b
4/4R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [PATCH v2 0/4] x86: don't default to executable mappings

Particularly for the 1:1 mapping it was pointed out that in order to limit the damage from security issues we should avoid mapping things executable when they don't need to be.

1: move syscall trampolines off the stack
2: emul: move stubs off the stack
3: move I/O emulation stubs off the stack
4: switch default mapping attributes to non-executable