Bug 506962

Summary: Kernel OOPS when receiving data over NFS and SELinux enabled
Product: [Fedora] Fedora Reporter: Lukáš Doktor <ldoktor>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 11CC: itamar, kernel-maint, quintela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-20 10:18:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukáš Doktor 2009-06-19 15:16:43 UTC
Description of problem:
Kernel OOPS when reciving data on NFS server with SELinux enabled. Another computer mounts NFS server shared folder and tries to copy there a lot of (small/medium/big) files (using cp). After couple of minutes it hangs up and on the NFS server is OOPS. When the kernel is booted with "selinux=0" it works fine (setenforce 0 is not enaugh, I had to reboot to get it copied).

Version-Release number of selected component (if applicable):
kernel-2.6.29.4-167.fc11.x86_64
nfs-utils-1.1.5-6.fc11.x86_64
nfs-utils-lib-1.1.4-6.fc11.x86_64
libselinux-2.0.80-1.fc11.x86_64
libselinux-python-2.0.80-1.fc11.x86_64
selinux-policy-3.6.12-39.fc11.noarch
libselinux-devel-2.0.80-1.fc11.x86_64
selinux-policy-3.6.12-45.fc11.noarch
libselinux-utils-2.0.80-1.fc11.x86_64


How reproducible:
Easily, it hanged-up many time in less than 5 minutes.

Steps to Reproduce:
1. Set-up NFS server, booted up with selinux, permissive or enforcing.
2. On another PC mount $NFS:/$SHARE /mnt
3. On another PC cp -R /home /mnt
4. Wait until OOPs on NFS server
  
Actual results:
OOPs on NFS server

Expected results:
Copied data from another PC to NFS server.

Additional info:
OOPs is reported there:
http://www.kerneloops.org/submitresult.php?number=465530

Another PC was in my case F9 with selinux disabled in grub (selinux=0)

Comment 1 Chuck Ebbert 2009-06-20 10:18:41 UTC

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