when oplocks is enable,kernel painc occurs when files are written. about ksmbd

[namjaejeon]

Ah, What client do you use ? I have never seen this issue before. Let me know how to reproduce. when I checked the backtrace, This is not SMB1.

[zztmy]

I use a Windows 10 client.

[hclee]

@zztmy
Could you elaborate how to reproduce it? Does this happen when copying files to ksmbd from Windows client?
Please show your smb.conf and what version of ksmbd and kernel.

[namjaejeon]

I wonder if you enabled oplock on smb1. And I wonder if there are two clients connected to smb1 and smb2/3 respectively.

[zztmy]

@hclee
Yes, it happens when you copy files from windows to ksmbd.

[global]
workgroup = WORKGROUP
netbios name = ZZTMY
map to guest = bad user
guest account = nobody
max active sessions = 128
bind interfaces only = yes
interfaces = br0
max open files = 1000
deadtime = 5
server min protocol = NT1
[zztmy]
path = /mnt/disk0/
guest ok = yes
writable = yes
oplocks = yes
force user = public_user

ksmbd version: 3.4.5
linux version: 5.10.107

@namjaejeon
Yes， that's the scene you're talking about.

[namjaejeon]

@zztmy Can you reproduce this issue easily ? I think you accessed the file through smb1 and smb2 clients at the same time. It looks like it needs to fix SMB1 code. Actually we don't want to touch smb1 code anymore. If you can tell us how to reproduce this, we'll check it.