Re: [PATCH v3] tgtd: refresh ready fds of event loop after event deletion

On 26/02/2014 07:13, Hitoshi Mitake wrote:
> For example, we can produce segfault of tgtd under heavy load. Below
> is a backtrace obtained from the core file:
>   (gdb) bt
>   #0  0x0000000000000000 in ?? ()
>   #1  0x0000000000411419 in event_loop () at tgtd.c:414
>   #2  0x0000000000411b65 in main (argc=<value optimized out>, argv=<value optimized out>) at tgtd.c:591
>
> To be honest, I still don't find an event handler which calls
> tgt_event_del() for other fds. But with this modification, the above
> segfault is avoided. The change seems to be effective.

Just want to make sure I follow --- you do have a way to reproduce the 
bug, but from code inspection you didn't find an event handler in tgt 
which calls  tgt_event_del() for "other" fds which is the trigger for 
the bug, right?

Can you please provide the steps to reproduce the bug?

Or.