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  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:	Mon, 5 Jan 2015 13:46:24 -0800
From:	Tony Luck <>
To:	Andy Lutomirski <>
Cc:	Borislav Petkov <>,
	Paul McKenney <>,
	X86 ML <>,
	Linus Torvalds <>,
	"" <>,
	Peter Zijlstra <>,
	Oleg Nesterov <>,
	Andi Kleen <>,
	Josh Triplett <>,
	Frédéric Weisbecker <>
Subject: Re: [PATCH v4 2/5] x86, traps: Track entry into and exit from IST context

On Wed, Dec 10, 2014 at 4:24 PM, Andy Lutomirski <> wrote:
> I think you need ist_begin_non_atomic() before local_irq_enable() and
> ist_end_non_atomic() after local_irq_disable().  Otherwise it should
> be good.

In your x86/paranoid branch you added:

     prev_state = ist_enter(regs);
          .... body of do_machine_check() here ...
     ist_exit(regs, prev_state);

Does that override the previous advice? Or do I still need something before
I call local_irq_enable() and after local_irq_disable()?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists