From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, linux-mm <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Anders Roxell <anders.roxell@linaro.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Evgenii Stepanov <eugenis@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Collingbourne <pcc@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Will Deacon <will@kernel.org>
Subject: [next] i386: kunit: ASSERTION FAILED at mm/kfence/kfence_test.c:547
Date: Fri, 29 Apr 2022 20:50:59 +0530 [thread overview]
Message-ID: <CA+G9fYu2kS0wR4WqMRsj2rePKV9XLgOU1PiXnMvpT+Z=c2ucHA@mail.gmail.com> (raw)
Following kernel regressions have been noticed on Linux next-20220426
(till date) on qemu_i386. This is a special build with KFENCE and KUNIT enabled
but not KASAN on i386.
snippet of Kconfigs from the build:
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_KFENCE=y
CONFIG_KFENCE_KUNIT_TEST=y
CONFIG_KUNIT=y
CONFIG_KUNIT_DEBUGFS=y
CONFIG_KUNIT_TEST=y
CONFIG_KUNIT_EXAMPLE_TEST=y
CONFIG_KUNIT_ALL_TESTS=y
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Regressions found on qemu_i386;:
- kunit/test_free_bulk
- kunit/test_memcache_typesafe_by_rcu
- kunit/test_out_of_bounds_read-memcache
- kunit/test_invalid_access
- kunit/test_krealloc
- kunit/test_invalid_addr_free
- kunit/test_gfpzero
- kunit/test_kmalloc_aligned_oob_write
- kunit/kfence
- kunit/test_out_of_bounds_read
- kunit/test_out_of_bounds_write
- kunit/test_invalid_addr_free-memcache
- kunit/test_double_free
- kunit/test_corruption-memcache
- kunit/test_use_after_free_read-memcache
- kunit/test_corruption
- kunit/test_use_after_free_read
- kunit/test_shrink_memcache
- kunit/test_double_free-memcache
- kunit/test_out_of_bounds_write-memcache
- kunit/test_kmalloc_aligned_oob_read
full test log link [1]
snippet of test log:
[ 4.168302] # test_free_bulk: test_alloc: size=271, gfp=cc0,
policy=right, cache=0
[ 4.271599] # test_free_bulk: test_alloc: size=271, gfp=cc0,
policy=none, cache=0
[ 4.271611] # test_free_bulk: test_alloc: size=271, gfp=cc0,
policy=left, cache=0
[ 4.687568] # test_free_bulk: test_alloc: size=271, gfp=cc0,
policy=none, cache=0
[ 4.687581] # test_free_bulk: test_alloc: size=271, gfp=cc0,
policy=none, cache=0
[ 4.687616] # test_free_bulk: ASSERTION FAILED at
mm/kfence/kfence_test.c:547
[ 4.687616] Expected report_available() to be false, but is true
[ 4.687789] not ok 13 - test_free_bulk
...
[ 33.294007] # test_memcache_typesafe_by_rcu: EXPECTATION FAILED
at mm/kfence/kfence_test.c:687
[ 33.294007] Expected report_matches(&expect) to be true, but is false
[ 33.294182] not ok 23 - test_memcache_typesafe_by_rcu
[ 33.294183] kunit_try_catch (209) used greatest stack depth: 5840 bytes left
[ 33.294619] # test_krealloc: test_alloc: size=32, gfp=cc0,
policy=any, cache=0
[ 33.391637] # test_krealloc: ASSERTION FAILED at
mm/kfence/kfence_test.c:724
[ 33.391637] Expected report_available() to be false, but is true
[ 33.391658] not ok 24 - test_krealloc
[ 33.391902] # test_memcache_alloc_bulk: setup_test_cache:
size=32, ctor=0x0
[ 33.495801] ok 25 - test_memcache_alloc_bulk
[ 33.495808] # kfence: pass:3 fail:20 skip:2 total:25
[ 33.495817] # Totals: pass:3 fail:20 skip:2 total:25
[ 33.495833] not ok 1 - kfence
metadata:
git_ref: master
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_sha: 088fb7eff3496e0f61fdf68bda89b81a4d0a4434
git_describe: next-20220426
kernel-config: https://builds.tuxbuild.com/28KafYBlDWOxI3qyNmGDwb63GuX/config
--
Linaro LKFT
https://lkft.linaro.org
[1] https://lkft.validation.linaro.org/scheduler/job/4950383#L770
[2] https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20220426/testrun/9235043/suite/kunit/test/test_use_after_free_read/log
next reply other threads:[~2022-04-29 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 15:20 Naresh Kamboju [this message]
2022-04-29 16:17 ` Marco Elver
2022-04-30 21:08 ` John Ogness
2022-05-02 7:51 ` Marco Elver
2022-05-02 8:30 ` Petr Mladek
2022-05-02 9:20 ` John Ogness
2022-05-03 7:42 ` Marco Elver
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='CA+G9fYu2kS0wR4WqMRsj2rePKV9XLgOU1PiXnMvpT+Z=c2ucHA@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=pcc@google.com \
--cc=ryabinin.a.a@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=vincenzo.frascino@arm.com \
--cc=will@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