From: Josh Triplett <josh@joshtriplett.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: paulmck@linux.vnet.ibm.com, Peter Zijlstra <peterz@infradead.org>,
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
Date: Sun, 22 Feb 2015 10:48:45 -0800 [thread overview]
Message-ID: <20150222184844.GA4262@thin> (raw)
In-Reply-To: <54EA207E.3090502@linux.intel.com>
On Sun, Feb 22, 2015 at 10:31:26AM -0800, Arjan van de Ven wrote:
> >>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.
Definitely not talking about malicious compromise here; malicious code
could just remove the write protection. However, write-protecting
kernel read-only data also protects against a class of bugs.
- Josh Triplett
next prev parent reply other threads:[~2015-02-22 18:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 5:08 [PATCH tip/core/rcu 0/4] Programmatic nestable expedited grace periods Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 1/4] rcu: Provide rcu_expedite_gp() and rcu_unexpedite_gp() Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 2/4] rcu: Add rcu_expedite_gp() and rcu_unexpedite_gp() to rcutorture Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 3/4] rcu: Update from rcu_expedited variable to rcu_gp_is_expedited() Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 4/4] rcu: Add Kconfig option to expedite grace periods during boot Paul E. McKenney
2015-02-20 9:11 ` [PATCH tip/core/rcu 0/4] Programmatic nestable expedited grace periods Peter Zijlstra
2015-02-20 16:37 ` Paul E. McKenney
2015-02-20 16:54 ` Peter Zijlstra
2015-02-20 17:14 ` Paul E. McKenney
2015-02-20 17:32 ` Arjan van de Ven
2015-02-20 17:43 ` Peter Zijlstra
2015-02-20 17:45 ` Arjan van de Ven
2015-02-21 16:08 ` Peter Zijlstra
2015-02-22 1:43 ` Paul E. McKenney
2015-02-20 18:38 ` Paul E. McKenney
2015-02-21 16:11 ` Peter Zijlstra
2015-02-21 17:59 ` Paul E. McKenney
2015-02-20 18:27 ` Paul E. McKenney
2015-02-20 18:29 ` Arjan van de Ven
2015-02-20 18:39 ` Paul E. McKenney
2015-02-21 15:51 ` Arjan van de Ven
2015-02-21 18:00 ` Paul E. McKenney
2015-02-22 3:58 ` Josh Triplett
2015-02-22 6:10 ` Paul E. McKenney
2015-02-22 18:31 ` Arjan van de Ven
2015-02-22 18:48 ` Josh Triplett [this message]
2015-02-21 6:04 ` Josh Triplett
2015-02-21 15:12 ` Mathieu Desnoyers
2015-02-21 23:58 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150222184844.GA4262@thin \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.