From: "Padhi, Beleswar" <b-padhi@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, <jassisinghbrar@gmail.com>,
<linux-kernel@vger.kernel.org>
Cc: <afd@ti.com>, <u-kumar1@ti.com>, <nm@ti.com>
Subject: Re: [PATCH 2/2] mailbox: ti-msgmgr: Read exact number of trailing message bytes
Date: Wed, 30 Sep 2026 12:07:45 +0530 [thread overview]
Message-ID: <de6aa05f-2226-4d7d-ae95-4da24135fee4@ti.com> (raw)
In-Reply-To: <170f362f-b64c-4b6f-9f74-ccfc4cce7d9e@ti.com>
On 9/30/2026 9:43 AM, Vignesh Raghavendra wrote:
>
> On 30/09/26 01:31, Beleswar Padhi wrote:
>> ti_msgmgr_send_data() copies the message to the data registers in u32
>> units. This has been harmless so far because the clients (TI-SCI)
>> always passed its preallocated message buffer, which is sized to the
>> maximum message size (60 or 64 bytes, a multiple of 4), so the extra
>> bytes read were still within the buffer. But, with a later TI-SCI
>> update, the message size can be varying now and not guaranteed to be a
>> multiple of 4, which would trigger KASAN out-of-bounds reports.
>>
>> Therefore, Build the trailing word by reading one byte at a time, only
>> up to the message length. The value written to the register is
>> unchanged.
>>
>> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
> This looks like a bug fixes and needs a Fixes: tag?
All mbox clients of ti-msgmgr currently send 60/64 byte sized messages.
So this
is not a bug today. It is only a preparatory patch for future mbox
clients which
can send message sizes like 19 bytes etc.
Thanks,
Beleswar
>
>> ---
>> drivers/mailbox/ti-msgmgr.c | 16 ++++++++++++----
>> 1 file changed, 12 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/mailbox/ti-msgmgr.c b/drivers/mailbox/ti-msgmgr.c
>> index 425d5f9d9d0e3..44457a896510f 100644
>> --- a/drivers/mailbox/ti-msgmgr.c
>> +++ b/drivers/mailbox/ti-msgmgr.c
>> @@ -425,10 +425,18 @@ static int ti_msgmgr_send_data(struct mbox_chan *chan, void *data)
>>
>> trail_bytes = message->len % sizeof(u32);
>> if (trail_bytes) {
>> - u32 data_trail = *word_data;
>> -
>> - /* Ensure all unused data is 0 */
>> - data_trail &= 0xFFFFFFFF >> (8 * (sizeof(u32) - trail_bytes));
>> + /*
>> + * Read the trailing bytes one at a time instead of as a full
>> + * u32, as the message buffer may end right after them and a
>> + * u32 read would go past the end of it. This also leaves all
>> + * unused data as 0.
>> + */
>> + u8 *byte_data = (u8 *)word_data;
>> + u32 data_trail = 0;
>> + int i;
>> +
>> + for (i = 0; i < trail_bytes; i++)
>> + data_trail |= byte_data[i] << (8 * i);
>> writel(data_trail, data_reg);
>> data_reg += sizeof(u32);
>> }
next prev parent reply other threads:[~2026-09-30 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 20:01 [PATCH 0/2] mailbox: ti-msgmgr: Fixes for polled rx and trailing bytes Beleswar Padhi
2026-09-29 20:01 ` [PATCH 1/2] mailbox: ti-msgmgr: Do not report rx poll timeout as a send failure Beleswar Padhi
2026-09-29 20:01 ` [PATCH 2/2] mailbox: ti-msgmgr: Read exact number of trailing message bytes Beleswar Padhi
2026-09-30 4:13 ` Vignesh Raghavendra
2026-09-30 6:37 ` Padhi, Beleswar [this message]
2026-09-30 15:04 ` Andrew Davis
2026-09-30 15:11 ` Padhi, Beleswar
2026-09-30 15:38 ` Andrew Davis
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=de6aa05f-2226-4d7d-ae95-4da24135fee4@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®