From: Eric Dumazet <eric.dumazet@gmail.com>
To: Matt Turner <mattst88@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
linux-nfs@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Manuel Lauss <manuel.lauss@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: NFS corruption, fixed by echo 1 > /proc/sys/vm/drop_caches -- next debugging steps?
Date: Fri, 08 Dec 2017 13:16:21 -0800 [thread overview]
Message-ID: <1512767781.25033.30.camel@gmail.com> (raw)
In-Reply-To: <CAEdQ38HEduSTY38Noj4peaMN_G++5sLJfqzCMkd3M4pPNTpU_Q@mail.gmail.com>
On Fri, 2017-12-08 at 12:26 -0800, Matt Turner wrote:
>
> Thanks for the quick reply!
>
> I tried the patch on top of master, but unfortunately the corruption
> still occurs.
You might try replacing in sbdma_add_rcvbuffer()
sb_new = netdev_alloc_skb(dev, size);
by
sb_new = alloc_skb(size, GFP_ATOMIC);
Maybe the device does not like having a frame spanning 2 pages.
next prev parent reply other threads:[~2017-12-08 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 1:43 NFS corruption, fixed by echo 1 > /proc/sys/vm/drop_caches -- next debugging steps? Matt Turner
2017-03-13 9:47 ` James Hogan
2017-03-13 17:17 ` Matt Turner
2017-03-15 9:25 ` Ralf Baechle
2017-12-08 7:00 ` Matt Turner
2017-12-08 7:54 ` Matt Turner
2017-12-08 13:42 ` Eric Dumazet
2017-12-08 13:52 ` Eric Dumazet
2017-12-08 20:26 ` Matt Turner
2017-12-08 21:16 ` Eric Dumazet [this message]
2017-12-09 21:03 ` Matt Turner
2017-12-09 21:37 ` Eric Dumazet
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=1512767781.25033.30.camel@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=edumazet@google.com \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-nfs@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=mattst88@gmail.com \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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