kasan-doc-note-kasanfault=panic_on_write-behaviour-for-async-modes.patch removed from -mm tree
The quilt patch titled
Subject: kasan, doc: note kasan.fault=panic_on_write behaviour for async modes
has been removed from the -mm tree. Its filename was
kasan-doc-note-kasanfault=panic_on_write-behaviour-for-async-modes.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Marco Elver <[email protected]>
Subject: kasan, doc: note kasan.fault=panic_on_write behaviour for async modes
Date: Tue, 20 Jun 2023 19:17:35 +0200
Note the behaviour of kasan.fault=panic_on_write for async modes, since all asynchronous faults will result in panic (even if they are reads).
---
Documentation/dev-tools/kasan.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/dev-tools/kasan.rst renamed from Documentation/dev-tools/kasan.rst~kasan-doc-note-kasanfault=panic_on_write-behaviour-for-async-modes +3 -1
@@ -110,7 +110,9 @@ parameter can be used to control panic a - ``kasan.fault=report``, ``=panic``, or ``=panic_on_write`` controls whether to only print a KASAN report, panic the kernel, or panic the kernel on invalid writes only (default: ``report``). The panic happens even if - ``kasan_multi_shot`` is enabled. + ``kasan_multi_shot`` is enabled. Note that when using asynchronous mode of + Hardware Tag-Based KASAN, ``kasan.fault=panic_on_write`` always panics on + asynchronously checked accesses (including reads). Software and Hardware Tag-Based KASAN modes (see the section about various modes below) support altering stack trace collection behavior:
_
Patches currently in -mm which might be from [email protected] are