linux-kernel - [GIT PULL] workqueue: fix possible deadlock on non-preemptive kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 30 Apr 2011 13:18:49 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>,
	Thilo-Alexander Ginkel <thilo@...kel.com>
Subject: [GIT PULL] workqueue: fix possible deadlock on non-preemptive
 kernels

(Sorry, the original posting was missing subject line.  Resending.)

Hello, Linus.

Please pull from the following branch to receive fix for a deadlock
which can happen between rescuers and stop_machine() while bringing
down CPUs on non-preemptive kernels.  The problem could be
half-reliably reproduced by Thilo-Alexander while the system is
entering suspend.  The branch also contains another commit which
documents workqueue debugging tricks.

The pull will cause conflict against 25985edced (Fix common
misspellings).  The fixed misspelling unfortunately was in the comment
which the fix replaces.  The conflict can be resolved by simply taking
the version from the fix commit.

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git fixes-2.6.39

Thank you.

Florian Mickler (1):
      workqueue: Document debugging tricks

Tejun Heo (1):
      workqueue: fix deadlock in worker_maybe_bind_and_lock()

 Documentation/workqueue.txt |   40 ++++++++++++++++++++++++++++++++++++++++
 kernel/workqueue.c          |    8 +++++++-
 2 files changed, 47 insertions(+), 1 deletions(-)

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/