linux-kernel - Re: WARNING: CPU: 0 PID: 0 at arch/x86/include/asm/kfence.h:46 kfence

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANpmjNOrZgBsgk1xxxz8-DrpnT0F0zyjin67=8_Ss7YZK-5_Mw@mail.gmail.com>
Date:   Mon, 21 Nov 2022 09:43:59 +0100
From:   Marco Elver <elver@...gle.com>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Dave Hansen <dave.hansen@...el.com>,
        Peter Zijlstra <peterz@...radead.org>,
        kasan-dev <kasan-dev@...glegroups.com>, X86 ML <x86@...nel.org>,
        open list <linux-kernel@...r.kernel.org>,
        linux-mm <linux-mm@...ck.org>, regressions@...ts.linux.dev,
        lkft-triage@...ts.linaro.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        Alexander Potapenko <glider@...gle.com>
Subject: Re: WARNING: CPU: 0 PID: 0 at arch/x86/include/asm/kfence.h:46 kfence_protect

On Mon, 21 Nov 2022 at 08:28, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>
> Hi Dave,
>
> On Fri, 18 Nov 2022 at 05:24, Dave Hansen <dave.hansen@...el.com> wrote:
> >
> > On 11/17/22 15:23, Marco Elver wrote:
> > > Yes - it's the 'level != PG_LEVEL_4K'.
> >
> > That plus the bisect made it pretty easy to find, thanks for the effort!
> >
> > Could you double-check that the attached patch fixes it?  It seemed to
> > for me.
>
> I have applied the attached patch on Linux next 20221118 and tested [1].
> The reported issue has been fixed now.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> Tested-by: Linux Kernel Functional Testing <lkft@...aro.org>
> Tested-by: Naresh Kamboju <naresh.kamboju@...aro.org>
>
> OTOH,
> I request you to walk through the boot and test log [1] (new see few failures).
>  not ok 7 - test_double_free
>  not ok 9 - test_invalid_addr_free
>  not ok 11 - test_corruption
>  not ok 18 - test_kmalloc_aligned_oob_write
>  # kfence: pass:19 fail:4 skip:2 total:25
>  # Totals: pass:19 fail:4 skip:2 total:25
>  not ok 6 - kfence

Fixed by https://lkml.kernel.org/r/20221118152216.3914899-1-elver@google.com