linux-kernel - Re: [PATCH] coresight: etm3x: Fix buffer overwrite in cntr_val

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: <15d536f2-0829-4f3f-b111-b15b14236bd2@linaro.org>
Date: Wed, 26 Nov 2025 15:33:22 +0000
From: James Clark <james.clark@...aro.org>
To: Mike Leach <mike.leach@...aro.org>, Leo Yan <leo.yan@....com>
Cc: Kuan-Wei Chiu <visitorckw@...il.com>, suzuki.poulose@....com,
 alexander.shishkin@...ux.intel.com, pratikp@...eaurora.org,
 mathieu.poirier@...aro.org, gregkh@...uxfoundation.org,
 jserv@...s.ncku.edu.tw, marscheng@...gle.com, ericchancf@...gle.com,
 milesjiang@...gle.com, nickpan@...gle.com, coresight@...ts.linaro.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] coresight: etm3x: Fix buffer overwrite in cntr_val_show()



On 26/11/2025 1:42 pm, Mike Leach wrote:
> Hi,
> 
> On Wed, 26 Nov 2025 at 12:31, Leo Yan <leo.yan@....com> wrote:
>>
>> On Wed, Nov 26, 2025 at 12:11:05PM +0000, James Clark wrote:
>>
>> [...]
>>
>>>> This fix can still be applied to older kernels, but seems to me that
>>>> now might be an appropriate time to consider removing the ETMv3 driver
>>>> from the mainline kernel?
>>>
>>> Yeah, if anyone is using it it would be on an old kernel surely?
>>
>> We can confirm this in another way: if I don't miss anything, over the
>> past several years (since 2017), we have not received any questions or
>> bug reports based on hands-on practice regarding ETMv3 on the Coresight
>> or perf mailing lists.
>>
>> Thanks,
>> Leo
> 
> The key to this is not the questions we are asked, but which platforms
> are still supported by the linux kernel.
> 
> The ETMv3 driver supports both ETMv3 and PTM trace (the programming
> model is the same, even if the trace decode is vastly different).
> 
> So as long as there are  platforms supported that use either of those,
> we need to keep the driver in.
> 
> Mike
> 

We're not running tests though, so if we find out it's fundamentally 
broken somehow it could be another justification to remove it, even if 
the kernel supports the devices. Do you have a board that you can test 
on Mike?

Maintenance hasn't been zero cost either, even build testing for arm32 
is annoying enough.