From: Johan Hovold <johan@kernel.org>
To: Ayush Singh <ayushdevel1325@gmail.com>
Cc: greybus-dev@lists.linaro.org, elder@kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
jkridner@beagleboard.org, kernel test robot <yujie.liu@intel.com>
Subject: Re: [PATCH V3] greybus: gb-beagleplay: Ensure le for values in transport
Date: Mon, 4 Dec 2023 15:12:14 +0100 [thread overview]
Message-ID: <ZW3ePt-c4Mu43DOV@hovoldconsulting.com> (raw)
In-Reply-To: <20231204131008.384583-1-ayushdevel1325@gmail.com>
On Mon, Dec 04, 2023 at 06:40:06PM +0530, Ayush Singh wrote:
> Ensure that the following values are little-endian:
> - header->pad (which is used for cport_id)
> - header->size
>
> Fixes: ec558bbfea67 ("greybus: Add BeaglePlay Linux Driver")
> 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>
> ---
> V3:
> - Fix endiness while sending.
> V2: https://lists.linaro.org/archives/list/greybus-dev@lists.linaro.org/thread/L53UN5ROSG4M6OE7CU5Y3L5F44T6ZPCC/
> - Ensure endianess for header->pad
> V1: https://lists.linaro.org/archives/list/greybus-dev@lists.linaro.org/message/K7UJ6PEAWBLNDMHLT2IO6OP5LQISHRUO/
>
> drivers/greybus/gb-beagleplay.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/greybus/gb-beagleplay.c b/drivers/greybus/gb-beagleplay.c
> index 43318c1993ba..8b21c3e1e612 100644
> --- a/drivers/greybus/gb-beagleplay.c
> +++ b/drivers/greybus/gb-beagleplay.c
> @@ -93,9 +93,9 @@ static void hdlc_rx_greybus_frame(struct gb_beagleplay *bg, u8 *buf, u16 len)
> memcpy(&cport_id, hdr->pad, sizeof(cport_id));
>
> dev_dbg(&bg->sd->dev, "Greybus Operation %u type %X cport %u status %u received",
> - hdr->operation_id, hdr->type, cport_id, hdr->result);
> + hdr->operation_id, hdr->type, le16_to_cpu(cport_id), hdr->result);
>
> - greybus_data_rcvd(bg->gb_hd, cport_id, buf, len);
> + greybus_data_rcvd(bg->gb_hd, le16_to_cpu(cport_id), buf, len);
This looks broken; a quick against mainline (and linux-next) check shows
cport_id to be u16.
I think you want get_unaligned_le16() or something instead of that
memcpy() above.
But that just begs the question: why has this driver repurposed the pad
bytes like this? The header still says that these shall be set to zero.
> }
>
> static void hdlc_rx_dbg_frame(const struct gb_beagleplay *bg, const char *buf, u16 len)
> @@ -340,14 +340,15 @@ static int gb_message_send(struct gb_host_device *hd, u16 cport, struct gb_messa
> {
> struct gb_beagleplay *bg = dev_get_drvdata(&hd->dev);
> struct hdlc_payload payloads[2];
> + __le16 cport_id = cpu_to_le16(cport);
>
> 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));
> + memcpy(msg->header->pad, &cport_id, sizeof(cport_id));
put_unaligned_le16(), if the driver should be messing with the pad
bytes like this at all...
>
> payloads[0].buf = msg->header;
> payloads[0].len = sizeof(*msg->header);
Johan
next prev parent reply other threads:[~2023-12-04 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 13:10 [PATCH V3] greybus: gb-beagleplay: Ensure le for values in transport Ayush Singh
2023-12-04 14:12 ` Johan Hovold [this message]
2023-12-04 16:28 ` Ayush Singh
2023-12-05 0:14 ` Greg KH
2023-12-05 11:45 ` Ayush Singh
2023-12-05 19:45 ` Greg KH
2023-12-05 20:32 ` Ayush Singh
2023-12-06 14:52 ` Alex Elder
2023-12-06 15:43 ` Ayush Singh
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=ZW3ePt-c4Mu43DOV@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=ayushdevel1325@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jkridner@beagleboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.