linux-kernel - Re: [PATCH 1/1] Fix HARD Lockup Firing off while in debugger

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

Date:	Sat, 12 Dec 2015 14:19:32 -0700
From:	Jeff Merkey <linux.mdb@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	akpm@...ux-foundation.org, uobergfe@...hat.com, dzickus@...hat.com,
	atomlin@...hat.com, cmetcalf@...hip.com, fweisbec@...il.com
Subject: Re: [PATCH 1/1] Fix HARD Lockup Firing off while in debugger

FYI.  More info, this bug only occurs when the processors have all
triggered on an int1 exception (do_debug) and are all spinning waiting
to access the debugger console .  It seems to be related to the nmi
handler firing off on processors which are waiting to get the shared
debugger lock in each debugger.

It does affect processors which may be in both nmi handlers and int1
handlers concurently but is triggered when more than one of the
processors has an outstanding int1 exception.
--
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/