Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <CACT4Y+beyZ7rjmy7im0KdSU-Pcqd4Rud3xsxonBbYVk0wU-B9g@mail.gmail.com>
 <20210311123315.GF37303@C02TD0UTHF1T.local>
In-Reply-To: <20210311123315.GF37303@C02TD0UTHF1T.local>
From:   Dmitry Vyukov <dvyukov@google.com>
Date:   Thu, 11 Mar 2021 17:56:46 +0100
Message-ID: <CACT4Y+ZPO7D1hGHZvuBQ52Vy2W7UUSW+YFE-Ax6-NMDnmrKTBA@mail.gmail.com>
Subject: Re: arm64 syzbot instances
To:     Mark Rutland <mark.rutland@arm.com>
Cc:     maz@kernel.org, Will Deacon <will@kernel.org>,
        Ard Biesheuvel <ardb@kernel.org>,
        Linux ARM <linux-arm-kernel@lists.infradead.org>,
        Arnd Bergmann <arnd@arndb.de>,
        syzkaller <syzkaller@googlegroups.com>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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