Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752120AbbBVSbu (ORCPT ); Sun, 22 Feb 2015 13:31:50 -0500 Received: from mga09.intel.com ([134.134.136.24]:25435 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752006AbbBVSbt (ORCPT ); Sun, 22 Feb 2015 13:31:49 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,626,1418112000"; d="scan'208";a="681660030" Message-ID: <54EA207E.3090502@linux.intel.com> Date: Sun, 22 Feb 2015 10:31:26 -0800 From: Arjan van de Ven User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Josh Triplett CC: paulmck@linux.vnet.ibm.com, Peter Zijlstra , linux-kernel@vger.kernel.org, mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com, akpm@linux-foundation.org, mathieu.desnoyers@efficios.com, tglx@linutronix.de, rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com Subject: Re: [PATCH tip/core/rcu 0/4] Programmatic nestable expedited grace periods References: <20150220050850.GA32639@linux.vnet.ibm.com> <20150220091107.GN21418@twins.programming.kicks-ass.net> <20150220163737.GL5745@linux.vnet.ibm.com> <20150220165409.GU5029@twins.programming.kicks-ass.net> <20150220171442.GM5745@linux.vnet.ibm.com> <54E76FB7.4060005@linux.intel.com> <20150220182745.GN5745@linux.vnet.ibm.com> <54E8A986.4090302@linux.intel.com> <20150222035806.GA4452@thin> In-Reply-To: <20150222035806.GA4452@thin> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 16 >> >> To show the boot time, I'm using the timestamp of the "Write protecting" line, >> that's pretty much the last thing we print prior to ring 3 execution. > > That's a little sad; we ought to be write-protecting kernel read-only > data as *early* as possible. well... if you are compromised before the first ring 3 instruction... .... you have a slightly bigger problem than where in the kernel we write protect things. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/