Skip to content

linux-user: Fix mincore() with PROT_NONE

Thomas Weißschuh qemu-devel 1 version Applied

Status from this message: Applied to my linux-user-for-8.1 branch.

Get series with b4
b4 am [email protected]

Versions newest first

  1. v2 Latest2 patches 5 repliesApplied

Changes in v2 from the cover letter

* Introduce symbolic flag VERIFY_NONE instead of hardcoding "0"

Patches in v2 Applied

#Subject and filesSizeRepliesApplied
1/2linux-user: Add new flag VERIFY_NONElinux-user/qemu.h+1 -02 replies
2/2linux-user: Don't require PROT_READ for mincorelinux-user/syscall.c+1 -12 replies

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchPhilippe Mathieu-DaudéLaurent Vivier
SeriesR-b
1/2R-b
2/2R-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/2] linux-user: Fix mincore() with PROT_NONE

The kernel does not require PROT_READ for addresses passed to mincore.

v1: https://lore.kernel.org/qemu-devel/[email protected]/
v1 -> v2:
* Introduce symbolic flag VERIFY_NONE instead of hardcoding "0"

Thomas Weißschuh (2):
linux-user: Add new flag VERIFY_NONE
linux-user: Don't require PROT_READ for mincore

 linux-user/qemu.h    | 1 +
 linux-user/syscall.c | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

base-commit: 1cc6e1a20144c0ae360cbeb0e035fdee1bd80609

Signature · 1 line
2.40.0