Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 4 Aug 2020 14:07:44 -0700
From:   Stephen Hemminger <stephen@networkplumber.org>
To:     "J. Bruce Fields" <bfields@fieldses.org>,
        Chuck Lever <chuck.lever@oracle.com>
Cc:     linux-nfs@vger.kernel.org
Subject: Fw: [Bug 208807] New: Problem with NFS kernel server code
Message-ID: <20200804140744.35ce4bdd@hermes.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk


Begin forwarded message:

Date: Tue, 04 Aug 2020 11:33:23 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 208807] New: Problem with NFS kernel server code


https://bugzilla.kernel.org/show_bug.cgi?id=208807

            Bug ID: 208807
           Summary: Problem with NFS kernel server code
           Product: Networking
           Version: 2.5
    Kernel Version: 5.8.0
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: nanook@eskimo.com
        Regression: No

Created attachment 290759
  --> https://bugzilla.kernel.org/attachment.cgi?id=290759&action=edit  
Output of dmesg while machine was dying

After about an hour and a half of operating on 5.8.0, one of our NFS servers
began to slow and basically ground to a halt.  Looks like a spinlock issue in
the NFS kernel server code.  I'll attach the output of dmesg while the machine
was dying in a file called "spinlock".  A shame because while it was running,
the performance of 5.8 was astounding.  Only the NFS servers seem to get ill,
the
client machines seem to run fine on 5.8 so far at least.

-- 
You are receiving this mail because:
You are the assignee for the bug.