NFSv3/TCP in 14.10 major issues and kernel NULL pointer dereference

Bug #1384659 reported by David
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Upgraded a NFS client to 14.10. Server is running FreeBSD 10.0, no changes on server from when client was running 14.04. Client is using NFSv3 over TCP.

Client hosts virtual machines - first virtual machine starts ok, second virtual machine starts but machine needs to fsck and reports timeouts, left overnight still cannot complete fsck. A simple "ls" of the NFS share hangs.

3.16.0-22-generic kernel kern.log generates warning and the Oops with null pointer dereference (see attached).

Tried mainline 3.16.6-031606-generic with same result (see attached). Same behaviour, fsck never finishes and ls hangs.

Tried mainline 3.14.22-031422-generic and problem is gone, fsck finishes in several seconds, no problems with ls, machine and VMs running normally since.

Revision history for this message
David (mardraum) wrote :
Revision history for this message
David (mardraum) wrote :
Brad Figg (brad-figg)
affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1384659

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: utopic
Revision history for this message
David (mardraum) wrote :

Installed a new host to test with and replicated the bug on it with 3.16.0-22-generic by installing a new VM - the Oops occurred during the grub2 install.

Installed 3.18.0-031800rc1-generic but the system will not even allow a VM to start, kworker and modprobe timeouts in kern.log.

tags: added: kernel-unable-to-test-upstream
Revision history for this message
David (mardraum) wrote :
Revision history for this message
David (mardraum) wrote :

Tried 3.16.7 mainline and can no longer reproduce the issue. The commit "NFS: Fix an uninitialised pointer Oops in the writeback error path" appears to be the fix.

tags: added: kernel-fixed-upstream
removed: kernel-unable-to-test-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tim Gardner (timg-tpi) wrote :

The next release of the Utopic kernel (3.16.0-25.33) will contain this patch.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.