On 05/03/2019 17:45, Andreas Schwab wrote:
> A zero-length read still needs to do the usual checks, thus it may return
> errors like EBADF. This makes the read syscall emulation consistent with
> the pread64 syscall emulation.
>
> Signed-off-by: Andreas Schwab
> ---
> linux-user/syscall.c | 4 +
Le 05/03/2019 à 17:45, Andreas Schwab a écrit :
> A zero-length read still needs to do the usual checks, thus it may return
> errors like EBADF. This makes the read syscall emulation consistent with
> the pread64 syscall emulation.
>
> Signed-off-by: Andreas Schwab
> ---
> linux-user/syscall.c
A zero-length read still needs to do the usual checks, thus it may return
errors like EBADF. This makes the read syscall emulation consistent with
the pread64 syscall emulation.
Signed-off-by: Andreas Schwab
---
linux-user/syscall.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
dif
On 09/11/2018 05:03 AM, Andreas Schwab wrote:
> +if (!(p = lock_user(VERIFY_WRITE, arg2, arg3, 0)))
> +goto efault;
The goto should not compile on head, after 2852aafd9d05.
r~
A zero-length read still needs to do the usual checks, thus it may return
errors like EBADF.
Signed-off-by: Andreas Schwab
---
linux-user/syscall.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 643b8833de
