[PATCH v3] linux-user: mprotect() should returns 0 when len is 0.

On Sat, Oct 8, 2022 at 12:41 AM Soichiro Isshiki wrote: > A validation for wrap-around was added, I think it is neccesory. I noticed the validation for wrap-around is *not* necessary, because it is done by guest_range_valid_untagged(). Signed-off-by: Soichiro Isshiki --- linux-user/mma

[PATCH v2] linux-user: mprotect() should returns 0 when len is 0.

rotect: Invalid argument OK OK mprotect: Invalid argument ``` seems good. Soichiro Isshiki Signed-off-by: sisshiki1969 --- linux-user/mmap.c | 13 - 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/linux-user/mmap.c b/linux-user/mmap.c index 28f3bc85ed..757709eeba 100644

[PATCH] linux-user: mprotect() should returns 0 when len is 0.

From: sisshiki1969 For now, qemu-x86_64 returns ENOMEM when mprotect() was called with an argument len is 0 from a guest process. This behavior is incompatible with the current Linux implementation, which mprotect() with len = 0 does nothing and returns 0, although it does not appear to be explic

[PATCH] linux-user: mprotect() should returns 0 when len is 0.

From: sisshiki1969 Signed-off-by: sisshiki1969 --- linux-user/mmap.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/linux-user/mmap.c b/linux-user/mmap.c index 28f3bc85ed..1ed79459ea 100644 --- a/linux-user/mmap.c +++ b/linux-user/mmap.c @@ -130,12 +130,12 @@ int targ