From d260249e707bef82e50614c32783a2afb808d8ea Mon Sep 17 00:00:00 2001 From: Marco Vanotti Date: Tue, 20 Nov 2018 20:56:43 -0800 Subject: sys/fuchsia: update VMAR syscalls * sys/fuchsia: update vmar syscalls. In a previous zircon commit[0], the vmar related syscalls (like `zx_vmar_map`, `zx_vmar_protect` and `zx_vmar_allocate`) changed the order of their parameters, making putting the flags parameter as the second parameter, and renaming it to "options". This commit modifies vmars.txt so that it reflects the latest state of the syscalls in zircon. I also modified the usage in `executor/common_fuchsia.h` I ran make extract, make generate and compiled syzkaller to test this change. [0]: https://fuchsia-review.googlesource.com/c/zircon/+/168060 * sys/fuchsia run make generate This commit is just the result of running make generate after its parent. This regenerates the definitions for the modified VMAR syscalls. --- pkg/csource/generated.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'pkg/csource') diff --git a/pkg/csource/generated.go b/pkg/csource/generated.go index a5124979b..181d0f9f5 100644 --- a/pkg/csource/generated.go +++ b/pkg/csource/generated.go @@ -819,9 +819,9 @@ long syz_mmap(size_t addr, size_t size) if (status != ZX_OK) return status; uintptr_t mapped_addr; - status = zx_vmar_map(root, addr - info.base, vmo, 0, size, - ZX_VM_FLAG_SPECIFIC_OVERWRITE | ZX_VM_FLAG_PERM_READ | - ZX_VM_FLAG_PERM_WRITE | ZX_VM_FLAG_PERM_EXECUTE, + status = zx_vmar_map(root, ZX_VM_FLAG_SPECIFIC_OVERWRITE | ZX_VM_FLAG_PERM_READ | ZX_VM_FLAG_PERM_WRITE | ZX_VM_FLAG_PERM_EXECUTE, + addr - info.base, vmo, 0, size, + &mapped_addr); return status; } -- cgit mrf-deployment