[Bugs] [Bug 1441474] synclocks don't work correctly under contention

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17043 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit f1a64f7c75fdc6a0ebea71ed2827d3dbc12761b5
Author: Jeff Darcy <jdarcy at redhat.com>
Date:   Mon Mar 20 12:31:33 2017 -0400

    core: fix synclocks' handling of "woken" flag

    The "woken" flag wasn't being reset when it should have been, leading
    (eventually) to a SEGV when someone tried to folow a synclock's waitq
    to a task structure that had been freed while still on the queue.  See
    the bug report for (far) more detail.

    Backport of:
    > Commit 31377765dbbb8d49292c4362837a695adcbc6cb4
    > BUG: 1434062
    > Reviewed-on: https://review.gluster.org/16926

    Change-Id: I5cd9ae1bcb831555274108b292181ec2a29b6d95
    BUG: 1441474
    Signed-off-by: Jeff Darcy <jeff at pl.atyp.us>
    Reviewed-on: https://review.gluster.org/17043
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>

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