Displaying 1 result from an estimated 1 matches for "smbd_smb2_request_next_incom".
2017 Mar 01
0
The connection would be broken when read rate is too big
...utes = yes
vfs objects = acl_xattr
socket options = TCP_NODELAY SO_RCVBUF=131072 SO_SNDBUF=131072
ctdbd socket = /var/run/ctdb/ctdbd.socket
log level = 2
security = user
I add some logs, found when the send queue is more than the max, it won’t allocate memory to the state->req in smbd_smb2_request_next_incoming function.
Then, the smbd_smb2_io_handler function mark the fd to not readable because state->req == NULL, and never mark it to readable again.
Then the Request Expiration Timer will break the connection.
I don’t know why the fd is marked to readable when the send queue is more than the max....