linux-kernel - Re: [PATCH v8 2/2] kasan: apply write-only mode in kasan kunit testcases

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: <9f332ea7-4210-42f8-b640-3135cdd808be@gmail.com>
Date: Thu, 18 Sep 2025 16:48:05 +0200
From: Andrey Ryabinin <ryabinin.a.a@...il.com>
To: Yeoreum Yun <yeoreum.yun@....com>, glider@...gle.com,
 andreyknvl@...il.com, dvyukov@...gle.com, vincenzo.frascino@....com,
 corbet@....net, catalin.marinas@....com, will@...nel.org,
 akpm@...ux-foundation.org, scott@...amperecomputing.com,
 jhubbard@...dia.com, pankaj.gupta@....com, leitao@...ian.org,
 kaleshsingh@...gle.com, maz@...nel.org, broonie@...nel.org,
 oliver.upton@...ux.dev, james.morse@....com, ardb@...nel.org,
 hardevsinh.palaniya@...iconsignals.io, david@...hat.com,
 yang@...amperecomputing.com
Cc: kasan-dev@...glegroups.com, workflows@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-mm@...ck.org
Subject: Re: [PATCH v8 2/2] kasan: apply write-only mode in kasan kunit
 testcases



On 9/17/25 12:27 AM, Yeoreum Yun wrote:
> When KASAN is configured in write-only mode,
> fetch/load operations do not trigger tag check faults.
> 
> As a result, the outcome of some test cases may differ
> compared to when KASAN is configured without write-only mode.
> 
> Therefore, by modifying pre-exist testcases
> check the write only makes tag check fault (TCF) where
> writing is perform in "allocated memory" but tag is invalid
> (i.e) redzone write in atomic_set() testcases.
> Otherwise check the invalid fetch/read doesn't generate TCF.
> 
> Also, skip some testcases affected by initial value
> (i.e) atomic_cmpxchg() testcase maybe successd if
> it passes valid atomic_t address and invalid oldaval address.
> In this case, if invalid atomic_t doesn't have the same oldval,
> it won't trigger write operation so the test will pass.
> 
> Signed-off-by: Yeoreum Yun <yeoreum.yun@....com>
> Reviewed-by: Andrey Konovalov <andreyknvl@...il.com>
> ---

Reviewed-by: Andrey Ryabinin <ryabinin.a.a@...il.com>