all: remove akaros support

Akaros support is unused, it was shutdown on syzbot for a while,
the akaros development seems to be frozen for years as well.
We have a bunch of hacks for Akaros since it supported
only super old gcc and haven't supported Go. Remove it.

6 files changed, 7 insertions, 31 deletions

diff --git a/docs/akaros/README.md b/docs/akaros/README.md
index ec89711bc..21da83805 100644
--- a/docs/akaros/README.md
+++ b/docs/akaros/README.md
@@ -1,18 +1,7 @@
 # Akaros support
 
-[Akaros](http://akaros.cs.berkeley.edu/) support is *incomplete*.
-
-See [Akaros getting started](https://github.com/brho/akaros/blob/master/GETTING_STARTED.md)
-re kernel building/running.
-
-Akaros does not support Go at the moment (except for a broken
-[1.3 port](https://github.com/akaros/go-akaros)). Full Go support is planned
-for Akaros. Until that happens running on Akaros is challenging. However,
-`syz-stress` can be run as follows:
-
-```shell
-make TARGETOS=linux syz-stress
-make TARGETOS=akaros SOURCEDIR=/akaros/checkout executor
-scp -P 5555 -i akaros_id_rsa -o IdentitiesOnly=yes bin/akaros_amd64/syz-executor  root@localhost:/
-bin/linux_amd64/syz-stress -os=akaros -ipc=pipe -procs=8 -executor "/usr/bin/ssh -p 5555 -i akaros_id_rsa -o IdentitiesOnly=yes root@localhost /syz-executor"
-```
+[Akaros](http://akaros.cs.berkeley.edu/) support was **removed**.
+You can find it in git history, if needed.
+Found bugs are [here](https://groups.google.com/forum/#!searchin/akaros/syzbot),
+[here](https://syzkaller.appspot.com/akaros)
+and [here](https://github.com/brho/akaros/issues?q=is%3Aissue+syzkaller).
diff --git a/docs/akaros/found_bugs.md b/docs/akaros/found_bugs.md
deleted file mode 100644
index 6c29b4487..000000000
--- a/docs/akaros/found_bugs.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Found bugs
-
-Most latest bugs are reported by [syzbot](/docs/syzbot.md) to
-[akaros](https://groups.google.com/forum/#!searchin/akaros/syzbot)
-mailing list and are listed on the [dashboard](https://syzkaller.appspot.com/akaros).
-
-_newer first_
-
-* [page fault in pipewrite](https://github.com/brho/akaros/issues/46)
-* [kernel panic in generic_file_write](https://github.com/brho/akaros/issues/44)
-* [assertion failed: page && pm_slot_check_refcnt(*page->pg_tree_slot)](https://github.com/brho/akaros/issues/42)
diff --git a/docs/found_bugs.md b/docs/found_bugs.md
index 1d00fcb26..56206fb5a 100644
--- a/docs/found_bugs.md
+++ b/docs/found_bugs.md
@@ -2,7 +2,7 @@
 
 [Linux kernel bugs](linux/found_bugs.md)
 
-[Akaros kernel bugs](akaros/found_bugs.md)
+[Akaros kernel bugs](akaros/README.md)
 
 [FreeBSD kernel bugs](freebsd/found_bugs.md)
 
diff --git a/docs/pseudo_syscalls.md b/docs/pseudo_syscalls.md
index 0eeff4e6c..c5df49ef1 100644
--- a/docs/pseudo_syscalls.md
+++ b/docs/pseudo_syscalls.md
@@ -29,7 +29,6 @@ one. These header files are defined in [gen.go](../pkg/csource/gen.go):
 
     executorFilenames := []string{
             "common_linux.h",
-            "common_akaros.h",
             "common_bsd.h",
             "common_fuchsia.h",
             "common_windows.h",
diff --git a/docs/setup.md b/docs/setup.md
index 7cf28908b..b55c4272e 100644
--- a/docs/setup.md
+++ b/docs/setup.md
@@ -3,7 +3,6 @@
 Generic setup instructions for fuzzing Linux kernel are outlined [here](linux/setup.md).
 
 For other kernels see:
-[Akaros](akaros/README.md),
 [FreeBSD](freebsd/README.md),
 [Darwin/XNU](darwin/README.md),
 [Fuchsia](fuchsia/README.md),
diff --git a/docs/syscall_descriptions.md b/docs/syscall_descriptions.md
index 9b4101a8b..fa1f41fbb 100644
--- a/docs/syscall_descriptions.md
+++ b/docs/syscall_descriptions.md
@@ -233,7 +233,7 @@ The second step is translation of descriptions into Go code using
 [pkg/ast](/pkg/ast/) and [pkg/compiler](/pkg/compiler/)).
 This step uses syscall descriptions and the const files generated during the first step
 and produces instantiations of `Syscall` and `Type` types defined in [prog/types.go](/prog/types.go).
-You can see an example of the compiler output for Akaros in `sys/akaros/gen/amd64.go`.
+You can see an example of the compiler output for Linux/AMD64 in `sys/linux/gen/amd64.go`.
 This step also generates some minimal syscall metadata for C++ code in `executor/syscalls.h`.
 
 ## Non-mainline subsystems