-
Notifications
You must be signed in to change notification settings - Fork 42
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Crashes with a Windows 10 client #193
Comments
Setting "oplocks = no" for the share seems to solve it. |
Can you reproduce this issue again ? Because kernel oops does not happen in ksmbd module. [Wed Jan 7 18:20:44 1970] PC is at apparmor_socket_sendmsg+0x18/0x20 |
Yes I tried the same after a reboot, and got the same result. For the 3rd attempt I disabled oplocks as above, and did not get the error that time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I upgraded my Windows client from Windows 7 to Windows 10, trying to run the same task as before (Windows Backup to the network share), but the ksmb server now crashes:
The text was updated successfully, but these errors were encountered: