From: Marco Elver <elver@google.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
kasan-dev <kasan-dev@googlegroups.com>, X86 ML <x86@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>
Subject: Re: WARNING: CPU: 0 PID: 0 at arch/x86/include/asm/kfence.h:46 kfence_protect
Date: Mon, 21 Nov 2022 09:43:59 +0100 [thread overview]
Message-ID: <CANpmjNOrZgBsgk1xxxz8-DrpnT0F0zyjin67=8_Ss7YZK-5_Mw@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYs3NLZgorPT33vu6XQ3HA6BpN_hL6GZWbfnirGYt1tNaQ@mail.gmail.com>
On Mon, 21 Nov 2022 at 08:28, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Hi Dave,
>
> On Fri, 18 Nov 2022 at 05:24, Dave Hansen <dave.hansen@intel.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@linaro.org>
> Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
> Tested-by: Naresh Kamboju <naresh.kamboju@linaro.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
next prev parent reply other threads:[~2022-11-21 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 11:31 Naresh Kamboju
2022-11-17 13:58 ` Marco Elver
2022-11-17 14:34 ` Dave Hansen
2022-11-17 23:23 ` Marco Elver
2022-11-17 23:54 ` Dave Hansen
2022-11-18 9:19 ` Marco Elver
2022-11-18 10:32 ` Peter Zijlstra
2022-11-21 7:28 ` Naresh Kamboju
2022-11-21 8:43 ` Marco Elver [this message]
2022-11-21 5:40 ` Naresh Kamboju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANpmjNOrZgBsgk1xxxz8-DrpnT0F0zyjin67=8_Ss7YZK-5_Mw@mail.gmail.com' \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox