linux-kernel - [PATCH 0/2] x86: Fix perf deadlock caused by dumpstack cleanup

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-next>] [day] [month] [year] [list]

Date:	Wed, 02 Apr 2014 13:26:39 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/2] x86: Fix perf deadlock caused by dumpstack cleanup

Linus,

Here are two patches that fix the deadlock that you discovered.

The first patch is the real culprit, but as I was looking at the code
I realized that the irq stack part was a bit off too. That part didn't
cause the lock up, but needs to be fixed regardless.

Note, I'm hoping to use these clean ups to make x86_64 and i386 code
a bit closer to each other, so I hope the original change does not
get reverted.

-- Steve

Steven Rostedt (Red Hat) (2):
      x86: Fix dumpstack_64 to keep state of "used" variable in loop
      x86: Fix dumpstack_64 irq stack handling

----
 arch/x86/kernel/dumpstack_64.c | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)
--
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/