Created attachment 292951 [details] output of dmesg we get i would say weekly crash in smb3_receive_transform: Call Trace: smb3_receive_transform+0x120/0x870 [cifs] cifs_demultiplex_thread+0xb53/0xc20 [cifs] ? cifs_handle_standard+0x190/0x190 [cifs] kthread+0x116/0x130 ? kthread_park+0x80/0x80 ret_from_fork+0x1f/0x30 share is mounted with: //hostname/data on /mnt/data type cifs (rw,relatime,vers=3.0,sec=ntlmsspi,cache=strict,multiuser,domain=swcznet2000,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.101.241,file_mode=0755,dir_mode=0755,seal,soft,nounix,mapposix,nohandlecache,noperm,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) an idea whats causing this? with kernel version 4.19 we got similar crashes.
I'm guessing that this happens when crypt_message() does not find the matching session. Success is returned, without decrypting the data. Will dig into it more.
some guesses: it seems, the oops seems to have started when more sessions (>10) where active and the host had longer uptimes (>24h). As "seal" seems non-standard i removed the mount parameter to avoid the oops. If the oops happens again, what can i do to better investigate the cause of the crash? The affected kernel is running as KVM-VM.
I believe the issue will be fixed by the fix mentioned above. The fix is already into the next kernel release. If it is possible for you to build the kernel from source, I can share the patch with you and you could verify that the fix works. I've already tested this by simulating the error. But nothing like testing in real-world, if it's happening consistently.
Here's the patch: https://git.samba.org/?p=sfrench/cifs-2.6.git;a=commit;h=9d05fc24b33bf285260d58b937b838b36530ea6d