From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 11 Dec 2018 19:47:16 -0000 Received: from mga14.intel.com ([192.55.52.115]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gWnzu-0006h6-M8 for speck@linutronix.de; Tue, 11 Dec 2018 20:47:15 +0100 Date: Tue, 11 Dec 2018 11:47:12 -0800 From: Andi Kleen Subject: [MODERATED] Re: [PATCH v2 3/8] MDSv2 5 Message-ID: <20181211194712.GD25620@tassilo.jf.intel.com> References: <0d6a3fbe4c511152a0f5350e62e9e09ec545f709.1544464266.git.ak@linux.intel.com> <20181211000303.GB16024@tassilo.jf.intel.com> <20181211032503.GB25620@tassilo.jf.intel.com> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: > > If it *does* set TIF_SCRUBME, we'll just re-do the scrub, and if it > > *doesn't* touch sensitive data, we'll return to the scrubbing having > > touched even more cachelines so any old sensitive data should be fine. Ah you mean we're ok if we recheck the flag with interrupts off at the end and repeat if needed? (like reschedule). I guess that will work. -Andi