[PATCH v5 000/144] smb: smbdirect/client/server: moving to common functions and smbdirect.ko

[Namjae Jeon]

>
> I tested with with mlx5_ib, irdma (roce) and rxe.
> There's still a known problem with iwarp.
Let me know what the known problem is.

>
> So far I can't see any regression compared the
> state before these 144 patches.
>
> Namjae, can you please test in your setup?

Is there any reason to print the log below by default?
ksmbd: smb_direct: smbdirect_socket_schedule_cleanup(-ESHUTDOWN)
called from smbdirect_socket_shutdown in line=650 status=LISTENING
ksmbd: smb_direct: smbdirect_socket_schedule_cleanup(-ESHUTDOWN)
called from smbdirect_socket_shutdown in line=650 status=LISTENING
ksmbd: smb_direct: smbdirect_socket_schedule_cleanup(-ESHUTDOWN)
called from smbdirect_socket_shutdown in line=650 status=CONNECTED
ksmbd: smb_direct: smbdirect_socket_schedule_cleanup(-ESHUTDOWN)
called from smbdirect_socket_shutdown in line=650 status=CONNECTED
ksmbd: smb_direct: status=ERROR first_error=-ESHUTDOWN => -ENOTCONN
ksmbd: smb_direct: smbdirect_socket_schedule_cleanup(-ESHUTDOWN)
called from smbdirect_socket_shutdown in line=650 status=CONNECTED
ksmbd: smb_direct: status=ERROR first_error=-ESHUTDOWN => -ENOTCONN
ksmbd: smb_direct: smbdirect_socket_schedule_cleanup(-ESHUTDOWN)
called from smbdirect_socket_shutdown in line=650 status=CONNECTED
ksmbd: smb_direct: status=ERROR first_error=-ESHUTDOWN => -ENOTCONN
ksmbd: smb_direct: status=DISCONNECTING first_error=-ESHUTDOWN => -ENOTCONN