[Bugs] [Bug 1582286] Brick-mux regressions failing on 4.1 branch

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1582286



--- Comment #10 from Shyamsundar <srangana at redhat.com> ---
(In reply to Atin Mukherjee from comment #6)
> Does the full backtrace of the glusterd core show the crash in urcu at the
> cleanup code path? If yes then this is known and isn’t a blocker. Othereise
> we need to look into it.

The stack is as in Problem 1 as detailed above.

The crash is in
https://github.com/gluster/glusterfs/blob/release-4.1/libglusterfs/src/event-epoll.c#L407
(an assert failure).

It does not seem to be a urcu related crash.

Here is another thread from the same dump that shows cleanup/exit is in
progress (
https://build.gluster.org/job/regression-on-demand-multiplex/47/console ), same
can be seen in the dump @
https://build.gluster.org/job/regression-on-demand-multiplex/45/console

For the record, in the last 5 runs this has not reappeared.

16:58:07 Thread 8 (Thread 0x7f9ead4e6700 (LWP 25850)):
16:58:07 #0  0x00007f9eb4df4a47 in sched_yield () from /lib64/libc.so.6
16:58:07 No symbol table info available.
16:58:07 #1  0x00007f9eb4d8ec09 in _IO_cleanup () from /lib64/libc.so.6
16:58:07 No symbol table info available.
16:58:07 #2  0x00007f9eb4d4ab8b in __run_exit_handlers () from /lib64/libc.so.6
16:58:07 No symbol table info available.
16:58:07 #3  0x00007f9eb4d4ac27 in exit () from /lib64/libc.so.6
16:58:07 No symbol table info available.
16:58:07 #4  0x0000000000408d61 in ?? ()
16:58:07 No symbol table info available.
16:58:07 #5  0x0000000000000001 in ?? ()
16:58:07 No symbol table info available.
16:58:07 #6  0x00000000000186c0 in ?? ()
16:58:07 No symbol table info available.
16:58:07 #7  0x00000000004146b0 in ?? ()
16:58:07 No symbol table info available.
16:58:07 #8  0x000000000000000f in ?? ()
16:58:07 No symbol table info available.
16:58:07 #9  0x0000000000000000 in ?? ()
16:58:07 No symbol table info available.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.