From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1EA903033C0 for ; Tue, 17 Mar 2026 03:36:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773718611; cv=none; b=Q+a9MyUOpLro12GZVBsYbumlzTHGzQkNJmkENSj09wrjL5h2q22zQGqAh5tHfnmGl8c9nQaNbraIwGW2E/36b2Q6ZsFl5tGO8vsPbyETl0ulU1lU5MD/1YaipQ+nOXqESP1wlnbuc4ae6gtdgAYAZKyTomGNexWiTL0RrXL1DwE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773718611; c=relaxed/simple; bh=cDbMvvfnswg/6UFIZf6AcKcJREuJJlm8VVo+mxym2Qo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=EDjJwTbJ0ZKfP/8LddYH5pBLzppF88x//hcLM9rCx17X22vehcgcbJv71GUwYhzdoZBpIk/ltno0ihnoAz8i8K23OlMo8O48CDf+uPcvoMa4ra4wrpIs2F4kXVY2PCkj7q3AeBQ53oY5eOppzfVTx6W8nZRwHEN+Lo+Big7xiAc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=TcC9BFK0; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="TcC9BFK0" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1773718609; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zB79a/FOENLHI8FCWiGrvfZkVLmqf3PzewX8k2/xZr0=; b=TcC9BFK0I6D9tCsikKVFGgvMK0rgEJVXrZhzwmjcTu/dZUaeCFuNTZjpMq5rIV/xJgSNGq HxxogFElamGFhBLpN+cuZV96YfLWY320m93kGagPRkeGpQxwxcEPX7fSKrNE/zNjrOHGKu f1HHh6RK9rheOKR9hlYKrsDBY/3kIa0= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-568-ivqPJgBFMnCWlq80myHG4g-1; Mon, 16 Mar 2026 23:36:42 -0400 X-MC-Unique: ivqPJgBFMnCWlq80myHG4g-1 X-Mimecast-MFC-AGG-ID: ivqPJgBFMnCWlq80myHG4g_1773718600 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 1AF9A195608B; Tue, 17 Mar 2026 03:36:39 +0000 (UTC) Received: from localhost (unknown [10.72.112.155]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 414B31800361; Tue, 17 Mar 2026 03:36:35 +0000 (UTC) Date: Tue, 17 Mar 2026 11:36:31 +0800 From: Baoquan He To: Samuel Holland Cc: kasan-dev@googlegroups.com, linux-mm@kvack.org, andreyknvl@gmail.com, ryabinin.a.a@gmail.com, glider@google.com, dvyukov@google.com, linux-kernel@vger.kernel.org, linux-um@lists.infradead.org, linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, x86@kernel.org, chris@zankel.net, jcmvbkbc@gmail.com, linux-s390@vger.kernel.org, hca@linux.ibm.com Subject: Re: [PATCH v5 14/15] mm/kasan: add document into kernel-parameters.txt Message-ID: References: <20260225081412.76502-1-bhe@redhat.com> <20260225081412.76502-15-bhe@redhat.com> Precedence: bulk X-Mailing-List: linux-s390@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 On 03/12/26 at 07:53am, Samuel Holland wrote: > Hi Baoquan, > > On 2026-02-25 2:14 AM, Baoquan He wrote: > > And also remove the relevant description in dev-tools/kasan.rst > > which is hw_tags specificially. > > > > Signed-off-by: Baoquan He > > --- > > Documentation/admin-guide/kernel-parameters.txt | 4 ++++ > > Documentation/dev-tools/kasan.rst | 2 -- > > 2 files changed, 4 insertions(+), 2 deletions(-) > > > > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > > index cb850e5290c2..e0115fad9e60 100644 > > --- a/Documentation/admin-guide/kernel-parameters.txt > > +++ b/Documentation/admin-guide/kernel-parameters.txt > > @@ -2899,6 +2899,10 @@ Kernel parameters > > js= [HW,JOY] Analog joystick > > See Documentation/input/joydev/joystick.rst. > > > > + kasan= [KNL] controls whether KASAN is enabled. > > + Format: off | on > > + default: on > > + > > kasan_multi_shot > > [KNL] Enforce KASAN (Kernel Address Sanitizer) to print > > report on every invalid memory access. Without this > > diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst > > index a034700da7c4..eaae83fcb5e4 100644 > > --- a/Documentation/dev-tools/kasan.rst > > +++ b/Documentation/dev-tools/kasan.rst > > @@ -129,8 +129,6 @@ Hardware Tag-Based KASAN mode is intended for use in production as a security > > mitigation. Therefore, it supports additional boot parameters that allow > > disabling KASAN altogether or controlling its features: > > The sentence above is now incorrect as well. I would recommend documenting the > parameter earlier in the "Boot parameters" section instead of removing it from > this document entirely. Good catch and the suggestion is good to me. Thanks. Is below change OK to you? >From 317be48b9c1bf9d33b8d8fff5e401e3155531d81 Mon Sep 17 00:00:00 2001 From: Baoquan He Date: Tue, 17 Mar 2026 11:28:39 +0800 Subject: [PATCH] mm/kasan: adjust documentation Content-type: text/plain To reflect the change of kasan=on|off. Signed-off-by: Baoquan He --- Documentation/dev-tools/kasan.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst index a034700da7c4..8e65bc04dbcd 100644 --- a/Documentation/dev-tools/kasan.rst +++ b/Documentation/dev-tools/kasan.rst @@ -103,6 +103,9 @@ Boot parameters KASAN is affected by the generic ``panic_on_warn`` command line parameter. When it is enabled, KASAN panics the kernel after printing a bug report. +The generic ``kasan=off`` or ``=on`` command line parameter controls +whether KASAN is enabled (default: ``on``). + By default, KASAN prints a bug report only for the first invalid memory access. With ``kasan_multi_shot``, KASAN prints a report on every invalid access. This effectively disables ``panic_on_warn`` for KASAN reports. @@ -127,9 +130,7 @@ modes below) support altering stack trace collection behavior: Hardware Tag-Based KASAN mode is intended for use in production as a security mitigation. Therefore, it supports additional boot parameters that allow -disabling KASAN altogether or controlling its features: - -- ``kasan=off`` or ``=on`` controls whether KASAN is enabled (default: ``on``). +controlling its features: - ``kasan.mode=sync``, ``=async`` or ``=asymm`` controls whether KASAN is configured in synchronous, asynchronous or asymmetric mode of -- 2.52.0