Messages in this thread | | | From | Dmitry Vyukov <> | Date | Thu, 11 Mar 2021 17:56:46 +0100 | Subject | Re: arm64 syzbot instances |
| |
On Thu, Mar 11, 2021 at 1:33 PM Mark Rutland <mark.rutland@arm.com> wrote: > > On Thu, Mar 11, 2021 at 12:38:21PM +0100, 'Dmitry Vyukov' via syzkaller wrote: > > Hi arm64 maintainers, > > Hi Dmitry, > > > We now have some syzbot instances testing arm64 (woohoo!) using qemu > > emulation. I wanted to write up the current status. > > Nice! > > > There are 3 instances, first uses KASAN: > > https://syzkaller.appspot.com/upstream?manager=ci-qemu2-arm64 > > second KASAN and 32-bit userspace test load (compat): > > https://syzkaller.appspot.com/upstream?manager=ci-qemu2-arm64-compat > > third uses MTE/KASAN_HWTAGS: > > https://syzkaller.appspot.com/upstream?manager=ci-qemu2-arm64-mte > > > > Kernel configs: > > https://github.com/google/syzkaller/blob/master/dashboard/config/linux/upstream-arm64-kasan.config > > https://github.com/google/syzkaller/blob/master/dashboard/config/linux/upstream-arm64-mte.config > > FWIW, I keep my fuzzing config fragment in my fuzzing/* branches on > git.kernel.org, and for comparison my fragment for v5.12-rc1 is: > > https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/commit/?h=fuzzing/5.12-rc1&id=6d9f7f8a2514fe882823fadbe7478228f71d7ab1 > > ... I'm not sure whether there's anything in that which is novel to you.
Hi Mark,
I've learned about DEBUG_TIMEKEEPING which we had disabled. I am enabling it. We also have CONTEXT_TRACKING_FORCE disabled. I don't completely understand what it's doing. Is it also "more debug checks" type of config?
FWIW we have more debug configs: https://github.com/google/syzkaller/blob/master/dashboard/config/linux/bits/debug.yml https://github.com/google/syzkaller/blob/master/dashboard/config/linux/bits/base.yml https://github.com/google/syzkaller/blob/master/dashboard/config/linux/bits/kasan.yml https://github.com/google/syzkaller/blob/master/dashboard/config/linux/bits/kmemleak.yml
| |