From: Kees Cook <kees@kernel.org>
To: Erhard Furtner <erhard_f@mailbox.org>
Cc: linux-mm@kvack.org, kasan-dev@googlegroups.com
Subject: Re: BUG: KASAN: vmalloc-out-of-bounds in vrealloc_noprof+0x195/0x220 at running fortify_kunit (v6.15-rc1, x86_64)
Date: Tue, 22 Apr 2025 09:50:24 -0700 [thread overview]
Message-ID: <202504220910.BAD42F0DC@keescook> (raw)
In-Reply-To: <20250421120408.04d7abdf@outsider.home>
On Mon, Apr 21, 2025 at 12:04:08PM +0200, Erhard Furtner wrote:
> fortify_test_alloc_size_kvmalloc_const test failure still in v6.15-rc3, also with a 'GCC14 -O2'-built kernel:
> [...]
> BUG: KASAN: vmalloc-out-of-bounds in vrealloc_noprof+0x2a2/0x370
> [...]
> not ok 7 fortify_test_alloc_size_kvmalloc_const
> [...]
> > I gave v6.15-rc1 a test ride on my Ryzen 5950 system with some debugging options turned on, getting a KASAN vmalloc-out-of-bounds hit at running fortify_kunit test:
I'm not able to reproduce this yet. What does your .config look like?
I tried this on Linus's latest and next-20250422:
$ gcc --version
gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-7)
...
$ ./tools/testing/kunit/kunit.py run \
--kconfig_add CONFIG_KASAN=y \
--kconfig_add CONFIG_KASAN_VMALLOC=y \
fortify
both showing passes:
[16:14:44] Testing complete. Ran 26 tests: passed: 26
What other debugging do you have enabled?
--
Kees Cook
next prev parent reply other threads:[~2025-04-22 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 17:25 BUG: KASAN: vmalloc-out-of-bounds in vrealloc_noprof+0x195/0x220 at running fortify_kunit (v6.15-rc1, x86_64) Erhard Furtner
2025-04-21 10:04 ` Erhard Furtner
2025-04-22 16:50 ` Kees Cook [this message]
2025-04-22 22:44 ` Erhard Furtner
2025-04-23 6:49 ` Kees Cook
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=202504220910.BAD42F0DC@keescook \
--to=kees@kernel.org \
--cc=erhard_f@mailbox.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.