From: Takashi Iwai <tiwai@suse.de>
To: Pravin Shelar <pshelar@nicira.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anupam Chanda <achanda@vmware.com>,
Tom Herbert <tom@herbertland.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 4.3-rc3 Regression: NFS access stall by commit 6ae459bdaaee
Date: Tue, 29 Sep 2015 12:33:00 +0200 [thread overview]
Message-ID: <s5hk2r9zfab.wl-tiwai@suse.de> (raw)
In-Reply-To: <CALnjE+rpcayxdyXwkDAqJeBgJUTOGACoGEKZRq=GhE+RDuF0OQ@mail.gmail.com>
On Tue, 29 Sep 2015 02:35:04 +0200,
Pravin Shelar wrote:
>
> On Mon, Sep 28, 2015 at 6:12 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > [I resent this since the previous mail didn't go out properly, as it
> > seems; apologies if you already read it, please disregard]
> >
> > Hi,
> >
> > I noticed that NFS access from my workstation slowed down drastically,
> > almost stalls, with the fresh 4.3-rc3. There are no particular kernel
> > errors / warnings.
> >
> > Then I performed git section, and it leaded to the commit:
> > 6ae459bdaaeebc632b16e54dcbabb490c6931d61
> > skbuff: Fix skb checksum flag on skb pull
> >
> > Reverting this commit from 4.3-rc3 fixed the issue indeed.
> >
> > Could you take a look at this? I added Trond to Cc in case he might
> > already know of it.
> >
> I send out fix for similar issue. Can you try the posted patch.
> https://patchwork.ozlabs.org/patch/523632/
Yes, the patch fixes the problem, thanks. Feel free to take my
tested-by tag:
Tested-by: Takashi Iwai <tiwai@suse.de>
But I guess the real fix is only the first chunk and the latter is
nothing but a cleanup? If so, it'd be better to split it.
Takashi
next prev parent reply other threads:[~2015-09-29 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5ha8s6bscn.wl-tiwai@suse.de>
2015-09-28 17:19 ` Pravin Shelar
2015-09-29 0:35 ` Pravin Shelar
2015-09-29 10:33 ` Takashi Iwai [this message]
2015-09-29 17:32 ` Pravin Shelar
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=s5hk2r9zfab.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=achanda@vmware.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=tom@herbertland.com \
--cc=trond.myklebust@primarydata.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®