-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kernel crash when modprobe nfsd module in the container , kernel version >= 5.3 #996
Comments
A kernel crash is a kernel problem. It looks like you are trying to load a kernel module from Ubuntu 20.04 tooling In the Ubuntu 18.04 kernel. Closing since this does not seem like a Docker issue. |
The module nfsd is the ubuntu 18.04 kernel,not the ubuntu 20.04. |
Ok but you are loading it from the 20.04 userspace. I really would not expect this to work. |
I have tested it in ubuntu 18.04 and 20.04. In the following three cases, the kernel has crashed.
But when i load nfsd module in the host userspace, it works well. And when i load other modules in the container, it also works well. A kernel crash is a kernel problem. It may be a nfsd problem. |
Yes indeed it could be related to nfsd in particular since it is being loaded into the kernel. |
I having the same problem on |
I will send a patch to the kernel nfsd maintainer. |
This is the patch:
|
Modprobe nfsd in the host of ubuntu 18.04, and then sync in the bash of the container or the host, it works well.
Modprobe nfsd in the container, and then sync in the bash of the container or the host, it hang...
The kernel version is from 5.3 to current.
The kernel image and the nfsd module are installed by apt.
Expected behavior
The sync cmd should work well.
Actual behavior
The sync cmd hang for a long long time,and the status of the sync process is disk sleep .
Steps to reproduce the behavior
In the host, disable the nfs-kernel-server.service, and reboot:
After reboot, docker pull image and run the image in the container:
In the container :
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
dmes:
This issue is found in the linux-lab of tinylab first, and we have tested it in the pwntools and the ubuntu, behaviors are the same, both on the hardware and the virtual box.
For more information, please visit the issue of linux-lab:
The text was updated successfully, but these errors were encountered: