linux-kernel - Re: [PATCH] coresight: Disable MMIO logging for coresight stm driver

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <5ccfe939-2764-4aa3-a485-e325333eca36@quicinc.com>
Date: Tue, 6 May 2025 11:13:09 +0800
From: Jinlong Mao <quic_jinlmao@...cinc.com>
To: Suzuki K Poulose <suzuki.poulose@....com>,
        Mike Leach
	<mike.leach@...aro.org>,
        James Clark <james.clark@...aro.org>,
        Alexander
 Shishkin <alexander.shishkin@...ux.intel.com>
CC: <coresight@...ts.linaro.org>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>
Subject: Re: [PATCH] coresight: Disable MMIO logging for coresight stm driver



On 2025/4/30 21:51, Suzuki K Poulose wrote:
> Hi,
> 
> On 30/04/2025 12:03, Mao Jinlong wrote:
>> When read/write registers with readl_relaxed and writel_relaxed,
>> log_read_mmio and log_write_mmio will be called. If mmio trace
>> is enabled to STM, STM driver will write the register to send the
>> trace and writel_relaxed will be called again. The circular call
>> like callstack below will happen. Disable mmio logging for stm
>> driver to avoid this issue.
>>
> 
> Thanks for the fix, looks good to me. However, I think the commit 
> description is a bit cryptic. Could we say :
> 
> With MMIO logging enabled, the MMIO access are traced and could be
> sent to an STM device. Thus, an STM driver MMIO access could create
> circular call chain with MMIO logging. Disable it for STM driver.
> 
> Suzuki

I will update it.

> 
>> [] stm_source_write[stm_core]+0xc4
>> [] stm_ftrace_write[stm_ftrace]+0x40
>> [] trace_event_buffer_commit+0x238
>> [] trace_event_raw_event_rwmmio_rw_template+0x8c
>> [] log_post_write_mmio+0xb4
>> [] writel_relaxed[coresight_stm]+0x80
>> [] stm_generic_packet[coresight_stm]+0x1a8
>> [] stm_data_write[stm_core]+0x78
>> [] ost_write[stm_p_ost]+0xc8
>> [] stm_source_write[stm_core]+0x7c
>> [] stm_ftrace_write[stm_ftrace]+0x40
>> [] trace_event_buffer_commit+0x238
>> [] trace_event_raw_event_rwmmio_read+0x84
>> [] log_read_mmio+0xac
>> [] readl_relaxed[coresight_tmc]+0x50
>>
>> Signed-off-by: Mao Jinlong <quic_jinlmao@...cinc.com>
>> ---
>>   drivers/hwtracing/coresight/Makefile | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/hwtracing/coresight/Makefile b/drivers/hwtracing/ 
>> coresight/Makefile
>> index 4ba478211b31..f3158266f75e 100644
>> --- a/drivers/hwtracing/coresight/Makefile
>> +++ b/drivers/hwtracing/coresight/Makefile
>> @@ -22,6 +22,8 @@ condflags := \
>>       $(call cc-option, -Wstringop-truncation)
>>   subdir-ccflags-y += $(condflags)
>> +CFLAGS_coresight-stm.o := -D__DISABLE_TRACE_MMIO__
>> +
>>   obj-$(CONFIG_CORESIGHT) += coresight.o
>>   coresight-y := coresight-core.o  coresight-etm-perf.o coresight- 
>> platform.o \
>>           coresight-sysfs.o coresight-syscfg.o coresight-config.o \
>