8:22 a.m.
It could very well mean that. I have no idea how it could happen, since
we always set events to EPOLLIN | EPOLLONESHOT (or on v3 and later
EPOLLOUT | EPOLLONESHOT | EPOLLET), and never set just EPOLLONESHOT.
That would indicate a kernel bug to me, I think.
Daniel
On 1/27/21 10:39 PM, anirban.chalcogen(a)gmail.com wrote:
Hi Daniel,
I noticed something odd about the /proc/[pid/fdinfo data we obtained at the time we
collected the core for ganesha. Basically, if you see here,
<pre>190:anon_inode:[eventpoll]
pos: 0
flags: 02000002
mnt_id: 10
tfd: 194 events: 40000000 data: c2
tfd: 196 events: 40000019 data: c4
tfd: 198 events: 40000019 data: c6
tfd: 189 events: 2019 data: bd
tfd: 200 events: 40000019 data: c8
191:socket:[426759494]
pos: 0
flags: 04002
mnt_id: 8
192:socket:[426759495]
pos: 0
flags: 04002
mnt_id: 8
193:anon_inode:[eventpoll]
pos: 0
flags: 02000002
mnt_id: 10
tfd: 192 events: 2019 data: c0
tfd: 199 events: 40000019 data: c7
tfd: 197 events: 40000019 data: c5
tfd: 195 events: 40000019 data: c3
tfd: 201 events: 40000019 data: c9
194:socket:[426759496]
pos: 0
flags: 04002
mnt_id: 8
195:socket:[426759497]
pos: 0
flags: 02
mnt_id: 8
</pre>
194 is the UDP socket. Iis is armed to the epoll_fd 190. If you see its event list, it
has only the EPOLLONESHOT event tagged to it and no EPOLLIN. Does that mean that somehow
we are left not listening of new messages on the UDP socket?
Thanks,
Anirban
_______________________________________________
Devel mailing list -- devel(a)lists.nfs-ganesha.org
To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org