linux-kernel - Re: [PATCH] coresight: fix the wrong type of the trace_id in coresight

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: <92dc9b50-5e58-4cfd-a78c-e32a4bec8e26@quicinc.com>
Date: Wed, 2 Apr 2025 08:50:06 +0800
From: Jie Gan <quic_jiegan@...cinc.com>
To: Mike Leach <mike.leach@...aro.org>,
        Anshuman Khandual
	<anshuman.khandual@....com>
CC: Jie Gan <jie.gan@....qualcomm.com>,
        Suzuki K Poulose
	<suzuki.poulose@....com>,
        James Clark <james.clark@...aro.org>,
        Tingwei Zhang
	<quic_tingweiz@...cinc.com>,
        Jinlong Mao <quic_jinlmao@...cinc.com>, <coresight@...ts.linaro.org>,
        <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
        <linux-arm-msm@...r.kernel.org>,
        "Dan
 Carpenter" <dan.carpenter@...aro.org>
Subject: Re: [PATCH] coresight: fix the wrong type of the trace_id in
 coresight_path



On 4/1/2025 5:56 PM, Mike Leach wrote:
> Hi,
> 
> On Tue, 1 Apr 2025 at 07:11, Anshuman Khandual
> <anshuman.khandual@....com> wrote:
>>
>> On 4/1/25 07:12, Jie Gan wrote:
>>> The trace_id in coresight_path may contain an error number which means a
>>> negative integer, but the current type of the trace_id is u8. Change the
>>> type to int to fix it.
>>>
>>> Reported-by: Dan Carpenter <dan.carpenter@...aro.org>
>>> Fixes: 3c03c49b2fa5 ("Coresight: Introduce a new struct coresight_path")
>>> Signed-off-by: Jie Gan <jie.gan@....qualcomm.com>
>>
>> LGTM
>>
>> Reviewed-by: Anshuman Khandual <anshuman.khandual@....com>
>>
>>> ---
>>>   include/linux/coresight.h | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/include/linux/coresight.h b/include/linux/coresight.h
>>> index d79a242b271d..c2bf10c43e7c 100644
>>> --- a/include/linux/coresight.h
>>> +++ b/include/linux/coresight.h
>>> @@ -337,7 +337,7 @@ static struct coresight_dev_list (var) = {                                \
>>>    */
>>>   struct coresight_path {
>>>        struct list_head        path_list;
>>> -     u8                      trace_id;
>>> +     int                     trace_id;
>>>   };
>>>
>>>   enum cs_mode {
> 
> There are many places in the Coresight drivers that assign a u8
> traceid from the path trace ID.
> 
> e.g.
> In coresight-etm4x-core.c : etm4_enable_perf()
> 
> drvdata->trcid = path->trace_id;
> 
> drvdata->trcid is defined as a u8  - the reason being trace IDs are
> 128 bits wide with some reserved values.
> 
> Will this not just trigger the same issue if path->trace_id is changed
> to an int? Even if not it is inconsistent handling of the trace ID
> values.
> 
> Trace ID errors should be handled by returning an invalid trace ID
> value - were the trace ID value will fail the macro
> IS_VALID_CS_TRACE_ID(), or separate the return of a trace ID from an
> error return in a function.
> 

Hi Mike,

The path->trace_id is verified after it has been assigned with the logic 
you mentioned:

if (!IS_VALID_CS_TRACE_ID(path->trace_id))
	goto err_path;

So it should be safe to assign to another u8 parameter, like you mentioned:

In coresight-etm4x-core.c : etm4_enable_perf()

drvdata->trcid = path->trace_id;

Thanks,
Jie


> Regards
> 
> Mike
> 
> 
> 
> --
> Mike Leach
> Principal Engineer, ARM Ltd.
> Manchester Design Centre. UK