linux-kernel - More hw_breakpoint scariness reduction

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]

Message-ID: <CALCETrXxs9gaFOb_DmwpawwGOeYj59PVDwk6Q-b7cuKCPjOuzg@mail.gmail.com>
Date:	Fri, 14 Aug 2015 15:38:32 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Peter Zijlstra <peterz@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	X86 ML <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Sasha Levin <sasha.levin@...cle.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Subject: More hw_breakpoint scariness reduction

Would you all consider it acceptable to disallow watchpoints on per
cpu data entirely?  I can think of a *lot* of places where hitting #DB
when accessing per cpu data from entry asm would be bad.

Of course, actually implementing that might be less than entirely fun,
given that a cpu could be onlined after creating a watchpoint.

--Andy

-- 
Andy Lutomirski
AMA Capital Management, LLC
--
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/