You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We encountered ganesha crashing in following stack:
but we don't think has bug in rbtree, and from gdb we found the request is unexpected:
Client don't mount nfs, but ganesha keeps receiving NFS 4.0 requests form this client(we always using nfsv4.1, so receiving nfsv4.0 is unexpected). And we wanted to catch nfs request through tcpdump both in client and ganesha, but failed, we only catch tcp pack :
(this is pcap catched from client: nfs.pcap.zip)
ganesha service port is 16194,form the pcap, we found client tried to send SYN firstly, and then send some tcp pack and finally send FIN.The above process will be repeated.
We wonder if ganesha may have misparsed the TCP packet as NFS request and lead to crushing?
I don't know if the community has encountered similar problems, and I hope to help analyze the reasons.
On the other hand, we will check why the client always has a TCP connection with ganesha.
The text was updated successfully, but these errors were encountered:
We encountered ganesha crashing in following stack:
but we don't think has bug in rbtree, and from gdb we found the request is unexpected:
Client don't mount nfs, but ganesha keeps receiving NFS 4.0 requests form this client(we always using nfsv4.1, so receiving nfsv4.0 is unexpected). And we wanted to catch nfs request through tcpdump both in client and ganesha, but failed, we only catch tcp pack :
(this is pcap catched from client: nfs.pcap.zip)
ganesha service port is 16194,form the pcap, we found client tried to send SYN firstly, and then send some tcp pack and finally send FIN.The above process will be repeated.
We wonder if ganesha may have misparsed the TCP packet as NFS request and lead to crushing?
I don't know if the community has encountered similar problems, and I hope to help analyze the reasons.
On the other hand, we will check why the client always has a TCP connection with ganesha.
The text was updated successfully, but these errors were encountered: