938949 – Update nfs-kernel-server-1.3.0-6.4: NFSv4-mounts no longer possible, rpc.mountd segfault

Bug 938949 - Update nfs-kernel-server-1.3.0-6.4: NFSv4-mounts no longer possible, rpc.mountd segfault

Summary: Update nfs-kernel-server-1.3.0-6.4: NFSv4-mounts no longer possible, rpc.moun...

Status:	RESOLVED DUPLICATE of bug 937039

Alias:	None

Product:	openSUSE Tumbleweed
Classification:	openSUSE
Component:	Network (show other bugs)
Version:	Current
Hardware:	x86-64 Other

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assignee:	Neil Brown
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2015-07-21 15:57 UTC by Forgotten User QFh0D9oMPg
Modified:	2015-07-22 03:23 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Forgotten User QFh0D9oMPg 2015-07-21 15:57:21 UTC

In my home net I use NFSv4 without any Kerberos and stuff, just plain sec=sys.

Since the update to nfs-kernel-server-1.3.0-6.4, clients can no longer mount any NFSv4 shares, they just hang when trying to access them. Downgrading to nfs-kernel-server-1.3.0-4.2.1 fixes the mounts again.

It seems that rpc.mountd segfaults:

Jul 21 17:46:40 server kernel: rpc.mountd[14002]: segfault at 0 ip 000055e69d77243f sp 00007ffdf46578e0 error 4 in rpc.mountd[55e69d767000+1a000]

Comment 1 Neil Brown 2015-07-22 03:23:07 UTC

This is fixed in Base:System and openSUSE:Factory.
Hopefully the fix will migrate into Tumbleweed soon.

*** This bug has been marked as a duplicate of bug 937039 ***