public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Ruidong Tian <tianruidong@linux.alibaba.com>
To: Umang Chheda <umang.chheda@oss.qualcomm.com>,
	Ruidong Tian <tianruidond@linux.alibaba.com>,
	Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	catalin.marinas@arm.com, will@kernel.org, lpieralisi@kernel.org,
	rafael@kernel.org, mark.rutland@arm.com,
	Sudeep Holla <sudeep.holla@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/8] ras: aest: Add panic_on_ue module parameter
Date: Wed, 6 May 2026 16:06:53 +0800	[thread overview]
Message-ID: <24e7a997-9479-447e-a1e2-cfab9a904668@linux.alibaba.com> (raw)
In-Reply-To: <20260505-aest-devicetree-support-v1-4-d5d6ffacf0a5@oss.qualcomm.com>



在 2026/5/5 20:23, Umang Chheda 写道:
> The driver unconditionally calls panic() whenever an unrecoverable,
> uncontainable UE (UET_UC or UET_UEU) is detected. There is no way
> for the user to suppress this behaviour, which makes it difficult to
> test UE injection or to run in environments where a kernel panic on
> every UE is undesirable.
> 
> Add a module parameter `aest_panic_on_ue` When set to 0 the driver
> logs the UE and continues instead of panicking.
> 
> Usage:
>    # Boot time (kernel cmdline)
>    aest.aest_panic_on_ue=0
> 
>    # Runtime
>    echo 0 > /sys/module/aest/parameters/aest_panic_on_ue
> 
> Signed-off-by: Umang Chheda <umang.chheda@oss.qualcomm.com>

Hi Umang,

Thanks for the patch.

I understand that this parameter is intended to facilitate UE injection 
testing and to avoid kernel panics in certain environments. However, we 
need to carefully consider the potential risks.

When a UC (Uncontainable Error) or UEU (Unrecoverable Error) occurs, the 
hardware state may be unpredictable, and data integrity cannot be 
guaranteed. Allowing the system to continue running instead of panicking 
in these scenarios could lead to silent data corruption or other 
unforeseen side effects, which poses a significant risk to system stability.

For the sake of robustness and data safety, I do not believe we should 
expose an interface that allows users to suppress panic on such critical 
errors.

If the goal is primarily to ease testing, I suggest handling this via 
local driver modifications in your test environment rather than 
upstreaming it as a configurable runtime option.

Best regards,
Ruidong

> ---
>   drivers/ras/aest/aest-core.c | 9 ++++++++-
>   1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/ras/aest/aest-core.c b/drivers/ras/aest/aest-core.c
> index b4f4c975da1d..9ce782a66edf 100644
> --- a/drivers/ras/aest/aest-core.c
> +++ b/drivers/ras/aest/aest-core.c
> @@ -22,6 +22,11 @@ DEFINE_PER_CPU(struct aest_device, percpu_adev);
>   #undef pr_fmt
>   #define pr_fmt(fmt) "AEST: " fmt
>   
> +static bool aest_panic_on_ue;
> +module_param(aest_panic_on_ue, bool, 0644);
> +MODULE_PARM_DESC(aest_panic_on_ue,
> +		 "Panic on unrecoverable error: 0=off 1=on (default: 1)");
> +
>   #ifdef CONFIG_DEBUG_FS
>   struct dentry *aest_debugfs;
>   #endif
> @@ -342,9 +347,11 @@ void aest_proc_record(struct aest_record *record, void *data, bool fake)
>   			aest_record_info(
>   				record,
>   				"Simulated error! Skip panic due to fault injection\n");
> -		else
> +		else if (aest_panic_on_ue)
>   			aest_panic(record, &regs,
>   				   "AEST: unrecoverable error encountered");
> +		else
> +			aest_record_err(record, "UE detected, panic suppressed\n");
>   	}
>   
>   	aest_log(record, &regs);
> 



  reply	other threads:[~2026-05-06  8:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 12:23 [PATCH 0/8] ras: aest: extend AEST support to Device Tree frontend Umang Chheda
2026-05-05 12:23 ` [PATCH 1/8] ras: aest: Fix shared processor node handling and error log messages Umang Chheda
2026-05-05 12:23 ` [PATCH 2/8] ras: aest: Fix CE/UE error counts not incrementing in debugfs Umang Chheda
2026-05-05 12:23 ` [PATCH 3/8] ras: aest: Skip unimplemented records " Umang Chheda
2026-05-05 12:23 ` [PATCH 4/8] ras: aest: Add panic_on_ue module parameter Umang Chheda
2026-05-06  8:06   ` Ruidong Tian [this message]
2026-05-05 12:23 ` [PATCH 5/8] dt-bindings: arm: ras: Introduce bindings for ARM AEST Umang Chheda
2026-05-05 12:23 ` [PATCH 6/8] ras: aest: Add DT frontend for ARM AEST RAS error sources Umang Chheda
2026-05-05 12:23 ` [PATCH 7/8] arm64: dts: qcom: lemans: add AEST error nodes Umang Chheda
2026-05-05 12:23 ` [PATCH 8/8] arm64: dts: qcom: monaco: " Umang Chheda
2026-05-06  8:10 ` [PATCH 0/8] ras: aest: extend AEST support to Device Tree frontend Ruidong Tian

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=24e7a997-9479-447e-a1e2-cfab9a904668@linux.alibaba.com \
    --to=tianruidong@linux.alibaba.com \
    --cc=andersson@kernel.org \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@kernel.org \
    --cc=tianruidond@linux.alibaba.com \
    --cc=tony.luck@intel.com \
    --cc=umang.chheda@oss.qualcomm.com \
    --cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox