From: David Miller <davem@davemloft.net>
To: LW@KARO-electronics.de
Cc: netdev@vger.kernel.org, rmk+kernel@arm.linux.org.uk,
Frank.Li@freescale.com, fabio.estevam@freescale.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: fec: fix regression on i.MX28 introduced by rx_copybreak support
Date: Tue, 07 Oct 2014 13:15:07 -0400 (EDT) [thread overview]
Message-ID: <20141007.131507.635415594538460008.davem@davemloft.net> (raw)
In-Reply-To: <1412687977-11742-1-git-send-email-LW@KARO-electronics.de>
From: Lothar Waßmann <LW@KARO-electronics.de>
Date: Tue, 7 Oct 2014 15:19:37 +0200
> commit 1b7bde6d659d ("net: fec: implement rx_copybreak to improve rx performance")
> introduced a regression for i.MX28. The swap_buffer() function doing
> the endian conversion of the received data on i.MX28 may access memory
> beyond the actual packet size in the DMA buffer. fec_enet_copybreak()
> does not copy those bytes, so that the last bytes of a packet may be
> filled with invalid data after swapping.
> This will likely lead to checksum errors on received packets.
> E.g. when trying to mount an NFS rootfs:
> UDP: bad checksum. From 192.168.1.225:111 to 192.168.100.73:44662 ulen 36
>
> Do the byte swapping and copying to the new skb in one go if
> necessary.
>
> Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de>
Why don't you just round up the length fec_enet_copybreak() uses when
need_swap is true? Then you will end up mimicking the original behavior
and not require this new helper function.
And in any case I agree with Sergei that if you do retain your approach,
the new 'swap' argument to fec_enet_copybreak() should be a 'bool'.
I'm really surprised there isn't a control register bit to adjust the
endianness of the data DMA'd to/from the network.
next prev parent reply other threads:[~2014-10-07 17:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 13:19 [PATCH] net: fec: fix regression on i.MX28 introduced by rx_copybreak support Lothar Waßmann
2014-10-07 13:31 ` David Laight
2014-10-07 14:17 ` Lothar Waßmann
2014-10-07 14:23 ` David Laight
2014-10-07 14:34 ` Eric Dumazet
2014-10-08 4:59 ` Lothar Waßmann
2014-10-07 14:02 ` Fabio Estevam
2014-10-07 14:27 ` Eric Dumazet
2014-10-07 14:41 ` David Laight
2014-10-08 5:01 ` Lothar Waßmann
2014-10-08 8:45 ` David Laight
2014-10-08 8:55 ` Lothar Waßmann
2014-10-07 16:07 ` Sergei Shtylyov
2014-10-08 8:54 ` David Laight
2014-10-08 9:12 ` Russell King - ARM Linux
2014-10-07 17:15 ` David Miller [this message]
2014-10-08 4:43 ` Lothar Waßmann
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=20141007.131507.635415594538460008.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Frank.Li@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=fabio.estevam@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).