executor, tools: rename SyzOS to SYZOS

4 files changed, 7 insertions, 7 deletions

diff --git a/executor/common_kvm_amd64.h b/executor/common_kvm_amd64.h
index a181e302e..ba3ef27e0 100644
--- a/executor/common_kvm_amd64.h
+++ b/executor/common_kvm_amd64.h
@@ -1155,7 +1155,7 @@ static void install_syzos_code(void* host_mem, size_t mem_size)
 {
 	size_t size = (char*)&__stop_guest - (char*)&__start_guest;
 	if (size > mem_size)
-		fail("SyzOS size exceeds guest memory");
+		fail("SYZOS size exceeds guest memory");
 	memcpy(host_mem, &__start_guest, size);
 }
 
diff --git a/executor/common_kvm_arm64.h b/executor/common_kvm_arm64.h
index 58678a9df..6442cb491 100644
--- a/executor/common_kvm_arm64.h
+++ b/executor/common_kvm_arm64.h
@@ -70,8 +70,8 @@ static void vm_set_user_memory_region(int vmfd, uint32 slot, uint32 flags, uint6
 #define ADRP_OPCODE 0x90000000
 #define ADRP_OPCODE_MASK 0x9f000000
 
-// Code loading SyzOS into guest memory does not handle data relocations (see
-// https://github.com/google/syzkaller/issues/5565), so SyzOS will crash soon after encountering an
+// Code loading SYZOS into guest memory does not handle data relocations (see
+// https://github.com/google/syzkaller/issues/5565), so SYZOS will crash soon after encountering an
 // ADRP instruction. Detect these instructions to catch regressions early.
 // The most common reason for using data relocaions is accessing global variables and constants.
 // Sometimes the compiler may choose to emit a read-only constant to zero-initialize a structure
@@ -81,7 +81,7 @@ static void validate_guest_code(void* mem, size_t size)
 	uint32* insns = (uint32*)mem;
 	for (size_t i = 0; i < size / 4; i++) {
 		if ((insns[i] & ADRP_OPCODE_MASK) == ADRP_OPCODE)
-			fail("ADRP instruction detected in SyzOS, exiting");
+			fail("ADRP instruction detected in SYZOS, exiting");
 	}
 }
 
@@ -89,7 +89,7 @@ static void install_syzos_code(void* host_mem, size_t mem_size)
 {
 	size_t size = (char*)&__stop_guest - (char*)&__start_guest;
 	if (size > mem_size)
-		fail("SyzOS size exceeds guest memory");
+		fail("SYZOS size exceeds guest memory");
 	memcpy(host_mem, &__start_guest, size);
 	validate_guest_code(host_mem, size);
 }
diff --git a/executor/common_kvm_arm64_syzos.h b/executor/common_kvm_arm64_syzos.h
index 2ef7819d9..5b50368dd 100644
--- a/executor/common_kvm_arm64_syzos.h
+++ b/executor/common_kvm_arm64_syzos.h
@@ -1219,7 +1219,7 @@ GUEST_CODE static void its_send_sync_cmd(uint64 cmdq_base, uint32 vcpu_id)
 }
 
 // This function is carefully written in a way that prevents jump table emission.
-// SyzOS cannot reference global constants, and compilers are very eager to generate a jump table
+// SYZOS cannot reference global constants, and compilers are very eager to generate a jump table
 // for a switch over GITS commands.
 // To work around that, we replace the switch statement with a series of if statements.
 // In addition, cmd->type is stored in a volatile variable, so that it is read on each if statement,
diff --git a/executor/test_linux.h b/executor/test_linux.h
index 6d36d201e..aab3529b8 100644
--- a/executor/test_linux.h
+++ b/executor/test_linux.h
@@ -314,7 +314,7 @@ static int test_syzos()
 		printf("mmap failed (%d)\n", errno);
 		return 1;
 	}
-	// Right now SyzOS testing just boils down to installing code into memory.
+	// Right now SYZOS testing just boils down to installing code into memory.
 	install_syzos_code(mem, mem_size);
 	munmap(mem, mem_size);
 	return 0;