[Bugs] [Bug 1412941] Regression caused by enabling client-io-threads by default

bugzilla at redhat.com bugzilla at redhat.com
Tue Jan 17 15:58:19 UTC 2017


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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/16396 committed in release-3.8 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit 9e3fea1e02b97781af6e6b46d8fd0fb6da47e6c9
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Sun Oct 9 21:36:40 2016 +0530

    performance/io-threads: Exit all threads on PARENT_DOWN

    Problem:
    When glfs_fini() is called on a volume where client.io-threads is enabled,
    fini() will free up iothread xl's private structure but there would be some
    threads that are sleeping which would wakeup after the timedwait completes
    leading to accessing already free'd memory.

    Fix:
    As part of parent-down, exit all sleeping threads.

    Please note that the upstream patch differs from this a little bit,
    because least-prio-throttling feature is removed from master, 3.9

     >BUG: 1381830
     >Change-Id: I0bb8d90241112c355fb22ee3fbfd7307f475b339
     >Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
     >Reviewed-on: http://review.gluster.org/15620
     >Smoke: Gluster Build System <jenkins at build.gluster.org>
     >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
     >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
     >Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
     >(cherry picked from commit d7a5ca16911caca03cec1112d4be56a9cda2ee30)

    BUG: 1412941
    Change-Id: I6341156251279b24ab2323cedf1b9722e42da671
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/16396
    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>

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


More information about the Bugs mailing list