Bug 120288 – 100% CPU usage

Bug 120288 - 100% CPU usage

Summary:	100% CPU usage

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	nfs-utils (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	James Morris
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	122683
	Show dependency tree / graph

Reported:	2004-04-07 12:03 EDT by Tim Waugh
Modified:	2007-11-30 17:10 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-12-01 09:08:57 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Tim Waugh 2004-04-07 12:03:46 EDT

Description of problem:
rpc.mountd/quotad use 100% CPU when started in enforcing mode.

Version-Release number of selected component (if applicable):
kernel-2.6.4-1.305
policy-1.10.1-2
nfs-utils-1.0.6-19.fc2

How reproducible:
100%

Steps to Reproduce:
1. Put something in /etc/exports (not sure if this is necessary)
2. setenforce 1
3. service nfs start

Comment 1 Gene Czarcinski 2004-04-15 04:35:48 EDT

This looks like a selinux security policy problem to me.  I cam CC'ing
Dan Walsh on this problem.

Comment 2 Daniel Walsh 2004-04-15 07:30:10 EDT

It is not  policy problem, but it is a SELinux/ Kernel problem.  NFS
server and SELinux don't play well together right now.  (NFS CLient
and SELinux aren't too freindly either, but they work somewhat).

Comment 3 Gene Czarcinski 2004-04-16 08:31:15 EDT

Interesting that if you setenforcing 0 you can mount from another
system but cpu is still 100%

Comment 4 Daniel Walsh 2004-12-01 09:08:57 EST

This seems to be working in FC3.

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