From: Catalin Marinas <catalin.marinas@arm.com>
To: kasan-dev@googlegroups.com, andreyknvl@gmail.com,
Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: dvyukov@google.com, vincenzo.frascino@arm.com,
ryabinin.a.a@gmail.com, glider@google.com, linux-mm@kvack.org,
Jiayuan Chen <jiayuan.chen@shopee.com>,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Yang Shi <yang@os.amperecomputing.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Huang Shijie <shijie@os.amperecomputing.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v1] kasan,mm: fix incomplete tag reset in change_memory_common()
Date: Thu, 8 Jan 2026 20:13:11 +0000 [thread overview]
Message-ID: <176790294571.2289790.2180517635826904022.b4-ty@arm.com> (raw)
In-Reply-To: <20260104123532.272627-1-jiayuan.chen@linux.dev>
(for some reason, I did not get this email, our server dropped it;
thanks to Will for telling me)
On Sun, 04 Jan 2026 20:35:27 +0800, Jiayuan Chen wrote:
> Running KASAN KUnit tests with {HW,SW}_TAGS mode triggers a fault in
> change_memory_common():
>
> Call trace:
> change_memory_common+0x168/0x210 (P)
> set_memory_ro+0x20/0x48
> vmalloc_helpers_tags+0xe8/0x338
> kunit_try_run_case+0x74/0x188
> kunit_generic_run_threadfn_adapter+0x30/0x70
> kthread+0x11c/0x200
> ret_from_fork+0x10/0x20
> ---[ end trace 0000000000000000 ]---
> # vmalloc_helpers_tags: try faulted
> not ok 67 vmalloc_helpers_tags
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] kasan,mm: fix incomplete tag reset in change_memory_common()
https://git.kernel.org/arm64/c/5fcd5513072b
--
Catalin
parent reply other threads:[~2026-01-08 20:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260104123532.272627-1-jiayuan.chen@linux.dev>]
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=176790294571.2289790.2180517635826904022.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=andreyknvl@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=dev.jain@arm.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=jiayuan.chen@linux.dev \
--cc=jiayuan.chen@shopee.com \
--cc=kasan-dev@googlegroups.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=shijie@os.amperecomputing.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
/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