diff options
| author | Andre Przywara <[email protected]> | 2021-03-19 16:53:27 +0000 |
|---|---|---|
| committer | Catalin Marinas <[email protected]> | 2021-03-24 15:43:01 +0000 |
| commit | 46cb11b17c7a917e0eb5c7aa87a7bc6cda455a5e (patch) | |
| tree | a0fc436b559c4c46dd17e32b33321bfdc4b5803b | |
| parent | 31c88729a7ad2b9871e6a73e491ec7223880d633 (diff) | |
kselftest/arm64: mte: user_mem: Fix write() warning
Out of the box Ubuntu's 20.04 compiler warns about missing return value
checks for write() (sys)calls.
Make GCC happy by checking whether we actually managed to write "val".
Signed-off-by: Andre Przywara <[email protected]>
Reviewed-by: Mark Brown <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Catalin Marinas <[email protected]>
| -rw-r--r-- | tools/testing/selftests/arm64/mte/check_user_mem.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tools/testing/selftests/arm64/mte/check_user_mem.c b/tools/testing/selftests/arm64/mte/check_user_mem.c index 4bfa80f2a8c3..1de7a0abd0ae 100644 --- a/tools/testing/selftests/arm64/mte/check_user_mem.c +++ b/tools/testing/selftests/arm64/mte/check_user_mem.c @@ -33,7 +33,8 @@ static int check_usermem_access_fault(int mem_type, int mode, int mapping) if (fd == -1) return KSFT_FAIL; for (i = 0; i < len; i++) - write(fd, &val, sizeof(val)); + if (write(fd, &val, sizeof(val)) != sizeof(val)) + return KSFT_FAIL; lseek(fd, 0, 0); ptr = mte_allocate_memory(len, mem_type, mapping, true); if (check_allocated_memory(ptr, len, mem_type, true) != KSFT_PASS) { |