From: Ayush Singh <ayushdevel1325@gmail.com>
To: Alex Elder <elder@ieee.org>, greybus-dev@lists.linaro.org
Cc: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org,
kernel test robot <yujie.liu@intel.com>
Subject: Re: [PATCH] greybus: gb-beagleplay: fix restricted __le16 degrades to integer warning
Date: Sun, 3 Dec 2023 12:47:15 +0530 [thread overview]
Message-ID: <32cf0a82-23b0-437e-b466-c05ceeb87da6@gmail.com> (raw)
In-Reply-To: <fea9d86b-54c7-493b-a7bd-8320bc2e8ced@ieee.org>
I apologize for the late response (college exams were going on).
I will go through the driver to find if any other endianness fixes are
needed.
As for `hdlc_payload->len`, the whole `hdlc_payload` is an abstraction
to store array length with the actual pointer. The len is never actually
sent over HDLC, so it should be fine.
Ayush Singh
On 11/14/23 20:27, Alex Elder wrote:
> On 11/14/23 8:01 AM, Ayush Singh wrote:
>> greybus message header->size are of type __le16, so to fix this warnings
>> we are using le16_to_cpu() macros.
>
> This is more than a warning, it's a bug (though it has no
> effect with a little-endian native CPU).
>
> I suggest you add:
>
> Fixes: ec558bbfea671 ("greybus: Add BeaglePlay Linux Driver")
>
> Should your hdlc_payload->len field be defined as little-endian?
> I've only scanned through this file at this point but I'm thinking
> there might be other endianness fixes needed as well.
>
> -Alex
>
>
>
>>
>> Reported-by: kernel test robot <yujie.liu@intel.com>
>> Closes: https://lore.kernel.org/r/202311072329.Xogj7hGW-lkp@intel.com/
>> Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>
>> ---
>> drivers/greybus/gb-beagleplay.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/greybus/gb-beagleplay.c
>> b/drivers/greybus/gb-beagleplay.c
>> index 43318c1993ba..b3f47b5cbbfa 100644
>> --- a/drivers/greybus/gb-beagleplay.c
>> +++ b/drivers/greybus/gb-beagleplay.c
>> @@ -344,7 +344,7 @@ static int gb_message_send(struct gb_host_device
>> *hd, u16 cport, struct gb_messa
>> dev_dbg(&hd->dev, "Sending greybus message with Operation %u,
>> Type: %X on Cport %u",
>> msg->header->operation_id, msg->header->type, cport);
>> - if (msg->header->size > RX_HDLC_PAYLOAD)
>> + if (le16_to_cpu(msg->header->size) > RX_HDLC_PAYLOAD)
>> return dev_err_probe(&hd->dev, -E2BIG, "Greybus message too
>> big");
>> memcpy(msg->header->pad, &cport, sizeof(cport));
>
prev parent reply other threads:[~2023-12-03 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 14:01 Ayush Singh
2023-11-14 14:57 ` Alex Elder
2023-12-03 7:17 ` Ayush Singh [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=32cf0a82-23b0-437e-b466-c05ceeb87da6@gmail.com \
--to=ayushdevel1325@gmail.com \
--cc=elder@ieee.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yujie.liu@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
all inboxes | Powered by JetHome®