From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Cc: jianqiang wang <wjq.sec@gmail.com>
Subject: [PATCH 3/5] net: ks8851_mll: do not read past the receive buffer
Date: Mon, 27 May 2024 09:29:13 +0200 [thread overview]
Message-ID: <20240527072915.3229221-3-s.hauer@pengutronix.de> (raw)
In-Reply-To: <20240527072915.3229221-1-s.hauer@pengutronix.de>
the hardware may report a packet longer than our receive buffer. Instead
of reading past the receive buffer, discard too long packets.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
drivers/net/ks8851_mll.c | 28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)
diff --git a/drivers/net/ks8851_mll.c b/drivers/net/ks8851_mll.c
index 2120657bd9..5e41888b28 100644
--- a/drivers/net/ks8851_mll.c
+++ b/drivers/net/ks8851_mll.c
@@ -420,6 +420,23 @@ static inline void ks_inblk(struct ks_net *ks, u16 *wptr, u32 len)
*wptr++ = (u16)readw(ks->hw_addr);
}
+/**
+ * ks_discardblk - read a block of data from QMU discarding the data
+ * @ks: The chip state
+ * @len: length in byte to read
+ *
+ * This discards a block of data, used when a packet is longer than our receive
+ * buffer. I don't know if it is necessary to discard the data like this, but
+ * it is the easy way out to fix the behaviour with too large packets without
+ * risking regressions.
+ */
+static inline void ks_discardblk(struct ks_net *ks, u32 len)
+{
+ len >>= 1;
+ while (len--)
+ (void)readw(ks->hw_addr);
+}
+
/**
* ks_outblk - write data to QMU.
* @ks: The chip information
@@ -676,9 +693,14 @@ static int ks8851_rx_frame(struct ks_net *ks)
tmp_rxqcr = ks_rdreg16(ks, KS_RXQCR);
ks_wrreg16(ks, KS_RXQCR, tmp_rxqcr | RXQCR_SDA);
- /* read 2 bytes for dummy, 2 for status, 2 for len*/
- ks_inblk(ks, ks->rx_buf, 2 + 2 + 2);
- ks_inblk(ks, ks->rx_buf, ALIGN(RxLen, 4));
+ if (RxLen <= PKTSIZE) {
+ /* read 2 bytes for dummy, 2 for status, 2 for len*/
+ ks_inblk(ks, ks->rx_buf, 2 + 2 + 2);
+ ks_inblk(ks, ks->rx_buf, ALIGN(RxLen, 4));
+ } else {
+ ks_discardblk(ks, 2 + 2 + 2 + ALIGN(RxLen, 4));
+ }
+
ks_wrreg16(ks, KS_RXQCR, tmp_rxqcr);
if (RxStatus & RXFSHR_RXFV) {
--
2.39.2
next prev parent reply other threads:[~2024-05-27 7:29 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
2024-05-27 9:34 ` Sascha Hauer
2024-05-27 7:29 ` Sascha Hauer [this message]
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=20240527072915.3229221-3-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--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