Linux CXL
 help / color / mirror / Atom feed
From: shaikh kamaluddin <shaikhkamal2012@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>, dan.j.williams@intel.com
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Shiju Jose <shiju.jose@huawei.com>,
	"Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>,
	"Steven Rostedt (Google)" <rostedt@goodmis.org>,
	Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
	linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PATCH] cxl: trace: Fix macro safety in CXL_EVT_TP_fast_assign
Date: Thu, 24 Apr 2025 21:18:24 +0530	[thread overview]
Message-ID: <896732b1-b761-4a07-a1c0-1e4456d36e84@gmail.com> (raw)
In-Reply-To: <68096119523f6_1bed7d294ad@iweiny-mobl.notmuch>


On 4/24/25 03:22, Ira Weiny wrote:
> shaikh.kamal wrote:
>> Fix checkpatch.pl detected error
>> The CXL_EVT_TP_fast_assign macro assigns multiple fields, but does not
>> wrap the body in a `do { ... } while (0)` block. This can lead to
>> unexpected behavior when used in conditional branches.
>>
>> Add checks to ensure cxlmd is valid before accessing its fields.
>>
>> Signed-off-by: shaikh.kamal <shaikhkamal2012@gmail.com>
> Nak
>
> This is not a normal macro.  checkpatch.pl does not apply in this case.
> Also checking cxlmd here is not necessary.  The callers of the tracepoint
> know very well that it needs to be valid.
>
> Ira
> Thanks for your comments.
>> ---
>>   drivers/cxl/core/trace.h | 30 ++++++++++++++++++------------
>>   1 file changed, 18 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/cxl/core/trace.h b/drivers/cxl/core/trace.h
>> index 25ebfbc1616c..a1a1014ee1fe 100644
>> --- a/drivers/cxl/core/trace.h
>> +++ b/drivers/cxl/core/trace.h
>> @@ -249,18 +249,24 @@ TRACE_EVENT(cxl_overflow,
>>   	__field(u8, hdr_maint_op_class)				\
>>   	__field(u8, hdr_maint_op_sub_class)
>>   
>> -#define CXL_EVT_TP_fast_assign(cxlmd, l, hdr)					\
>> -	__assign_str(memdev);				\
>> -	__assign_str(host);			\
>> -	__entry->log = (l);							\
>> -	__entry->serial = (cxlmd)->cxlds->serial;				\
>> -	__entry->hdr_length = (hdr).length;					\
>> -	__entry->hdr_flags = get_unaligned_le24((hdr).flags);			\
>> -	__entry->hdr_handle = le16_to_cpu((hdr).handle);			\
>> -	__entry->hdr_related_handle = le16_to_cpu((hdr).related_handle);	\
>> -	__entry->hdr_timestamp = le64_to_cpu((hdr).timestamp);			\
>> -	__entry->hdr_maint_op_class = (hdr).maint_op_class;			\
>> -	__entry->hdr_maint_op_sub_class = (hdr).maint_op_sub_class
>> +#define CXL_EVT_TP_fast_assign(cxlmd, l, hdr) \
>> +	do { \
>> +		if (!(cxlmd)) { \
>> +			pr_err("Invalid arguments to CXL_EVT_TP_fast_assign\n"); \
>> +			break; \
>> +		} \
>> +		__assign_str(memdev); \
>> +		__assign_str(host); \
>> +		__entry->log = (l); \
>> +		__entry->serial = (cxlmd)->cxlds->serial; \
>> +		__entry->hdr_length = (hdr).length; \
>> +		__entry->hdr_flags = get_unaligned_le24((hdr).flags); \
>> +		__entry->hdr_handle = le16_to_cpu((hdr).handle); \
>> +		__entry->hdr_related_handle = le16_to_cpu((hdr).related_handle); \
>> +		__entry->hdr_timestamp = le64_to_cpu((hdr).timestamp); \
>> +		__entry->hdr_maint_op_class = (hdr).maint_op_class; \
>> +		__entry->hdr_maint_op_sub_class = (hdr).maint_op_sub_class; \
>> +	} while (0)
>>   
>>   #define CXL_EVT_TP_printk(fmt, ...) \
>>   	TP_printk("memdev=%s host=%s serial=%lld log=%s : time=%llu uuid=%pUb "	\
>> -- 
>> 2.43.0
>>
>

      reply	other threads:[~2025-04-24 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 18:45 [PATCH] [PATCH] cxl: trace: Fix macro safety in CXL_EVT_TP_fast_assign shaikh.kamal
2025-04-21 19:12 ` Steven Rostedt
2025-04-24 15:47   ` shaikh kamaluddin
2025-04-23 21:52 ` Ira Weiny
2025-04-24 15:48   ` shaikh kamaluddin [this message]

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=896732b1-b761-4a07-a1c0-1e4456d36e84@gmail.com \
    --to=shaikhkamal2012@gmail.com \
    --cc=Smita.KoralahalliChannabasappa@amd.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=fabio.m.de.francesco@linux.intel.com \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shiju.jose@huawei.com \
    --cc=vishal.l.verma@intel.com \
    /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