mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: festevam@gmail.com
Cc: LW@karo-electronics.de, netdev@vger.kernel.org,
	fabio.estevam@freescale.com, Frank.Li@freescale.com,
	linux-kernel@vger.kernel.org, rmk+kernel@arm.linux.org.uk,
	linux-arm-kernel@lists.infradead.org, stefan.wahren@i2se.com
Subject: Re: [PATCHv4 1/1] net: fec: fix regression on i.MX28 introduced by rx_copybreak support
Date: Fri, 07 Nov 2014 12:09:26 -0500 (EST)	[thread overview]
Message-ID: <20141107.120926.297493918093719160.davem@davemloft.net> (raw)
In-Reply-To: <CAOMZO5Cb1=Nvzu8EHqmV+K+W+ZJxzL1=5MnK6hDSstwh9ruweA@mail.gmail.com>

From: Fabio Estevam <festevam@gmail.com>
Date: Fri, 7 Nov 2014 10:26:15 -0200

> On Fri, Nov 7, 2014 at 7:02 AM, Lothar Waßmann <LW@karo-electronics.de> wrote:
>> 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>
> 
> With this patch I am able to NFS mount on mx28 again. Thanks, Lothar!
> 
> Tested-by: Fabio Estevam <fabio.estevam@freescale.com>

Applied, thanks everyone.

      reply	other threads:[~2014-11-07 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  9:02 [PATCHv4 0/1] " Lothar Waßmann
2014-11-07  9:02 ` [PATCHv4 1/1] " Lothar Waßmann
2014-11-07 12:26   ` Fabio Estevam
2014-11-07 17:09     ` David Miller [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=20141107.120926.297493918093719160.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Frank.Li@freescale.com \
    --cc=LW@karo-electronics.de \
    --cc=fabio.estevam@freescale.com \
    --cc=festevam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=stefan.wahren@i2se.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®