From: "Jules Maselbas" <jmaselbas@zdiv.net>
To: "Sascha Hauer" <s.hauer@pengutronix.de>,
"Barebox List" <barebox@lists.infradead.org>
Cc: "jianqiang wang" <wjq.sec@gmail.com>
Subject: Re: [PATCH 2/5] net: cs8900: do not read past the receive buffer
Date: Mon, 27 May 2024 10:58:55 +0200 [thread overview]
Message-ID: <D1KAXE1FR9NJ.XQQM6JG3M6F7@zdiv.net> (raw)
In-Reply-To: <20240527072915.3229221-2-s.hauer@pengutronix.de>
Hi Sascha,
Just a quick remark:
On Mon May 27, 2024 at 9:29 AM CEST, Sascha Hauer wrote:
> the hardware may report a packet longer than our receive buffer. Instead
> of reading past the read buffer, discard too long packets.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> drivers/net/cs8900.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/cs8900.c b/drivers/net/cs8900.c
> index afb0f3e26e..a96b574f95 100644
> --- a/drivers/net/cs8900.c
> +++ b/drivers/net/cs8900.c
> @@ -295,8 +295,13 @@ static int cs8900_recv(struct eth_device *dev)
> status = readw(priv->regs + CS8900_RTDATA0);
> len = readw(priv->regs + CS8900_RTDATA0);
>
> - for (addr = (u16 *)priv->rx_buf, i = (len + 1) >> 1; i > 0; i--)
> - *addr++ = readw(priv->regs + CS8900_RTDATA0);
> + if (len <= PKTSIZE) {
> + for (addr = (u16 *)priv->rx_buf, i = (len + 1) >> 1; i > 0; i--)
> + *addr++ = readw(priv->regs + CS8900_RTDATA0);
> + } else {
> + for (addr = (u16 *)priv->rx_buf, i = (len + 1) >> 1; i > 0; i--)
> + (void)readw(priv->regs + CS8900_RTDATA0);
So the packet is "discarded" here but the function doesn't returns with an error
and proceed to call net_received with the previous (if any) packet but with the
new length ...
I am not sure if this is an issue or not.
> + }
>
> net_receive(dev, priv->rx_buf, len);
>
best,
Jules
next prev parent reply other threads:[~2024-05-27 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 7:29 [PATCH 1/5] net: cs8900: simplify buffer read loop Sascha Hauer
2024-05-27 7:29 ` [PATCH 2/5] net: cs8900: do not read past the receive buffer Sascha Hauer
2024-05-27 8:58 ` Jules Maselbas [this message]
2024-05-27 9:34 ` Sascha Hauer
2024-05-27 7:29 ` [PATCH 3/5] net: ks8851_mll: " Sascha Hauer
2024-05-27 7:29 ` [PATCH 4/5] net: liteeth: " Sascha Hauer
2024-05-27 7:29 ` [PATCH 5/5] net: smc911x: " Sascha Hauer
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=D1KAXE1FR9NJ.XQQM6JG3M6F7@zdiv.net \
--to=jmaselbas@zdiv.net \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=wjq.sec@gmail.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