[Bugs] [Bug 1423065] Deadlock in gf_timer calls and a possible core ( illegal memory access) in AFR on dropping FUSE cache

[bugzilla at redhat.com]

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

Ravishankar N <ravishankar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |srangana at redhat.com
              Flags|                            |needinfo?(srangana at redhat.c
                   |                            |om)



--- Comment #4 from Ravishankar N <ravishankar at redhat.com> ---
----------------------------
Notes to self:
(gdb) p *ctx
$4 = {read_subvol = 4379182848, spb_choice = -1, timer = 0x2b1a134558a5f533,
need_refresh = (_gf_true | unknown: 1487271126)}

ctx->timer is not NULL. But ctx->timer is initialized only when split-brain
resolution related setfattr commands are executed from mount, which was not
done here in the test run.

ctx->read_subvol is supposed to be a bit map array of readable subvols
(https://github.com/gluster/glusterfs/blob/v3.10.0rc0/xlators/cluster/afr/src/afr-common.c#L162)
but the value 4379182848 in this case when converted to binary to get the
data/metadata/event_gen bits in the bitmap is giving gibberish results

ctx->need_refresh not being just _gf_true (i.e 0x01) but a large non zero value
(1487271126) is again gibberish.
----------------------------
Shyam, it looks like the inode context values are corrupt here and the problem
is likely to be BZ 1423385 where the inode context of a different xlator is
returned when we get it with a key of a given xlator. (I don't see any bug in
AFR itself from a looking at the code).

Can you wait until https://review.gluster.org/#/c/16655/ gets merged to see if
it fixes the problem?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=j17Qxy6Vwm&a=cc_unsubscribe