From: Arjan van de Ven <arjan@infradead.org>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: Brian Gerst <bgerst@didntduck.org>,
"Jonathan M. McCune" <jonmccune@cmu.edu>,
linux-kernel@vger.kernel.org,
Arvind Seshadri <arvinds@cs.cmu.edu>, Bryan Parno <parno@cmu.edu>
Subject: Re: using segmentation in the kernel
Date: Wed, 12 Oct 2005 11:05:35 +0200 [thread overview]
Message-ID: <1129107936.3082.34.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <434C1F8E.6080405@gmail.com>
On Tue, 2005-10-11 at 22:24 +0200, Alon Bar-Lev wrote:
> Brian Gerst wrote:
> > Jonathan M. McCune wrote:
> >
> >> Hello,
> >>
> > Why send the kernel back to the 2.0 days? There is no valid reason for
> > doing this with they way x86 segmentation works, which is why it was
> > done away with in 2.1.
> >
>
> But with segmentation you can set code to be read-only,
you can do that without segmentation too, absolutely no problem
> disallow execution from stack,
That is why CPUs have NX nowadays. And it's not like the kernel is full
of buffer overflows; due to the 4Kb stack space (total), there are very
very few static buffers on the stack at all; simply because theres no
space to do it.
> separate modules so that they
> will not affect kernel and more...
and I don't believe this one yota. THe only way to do this is to run
modules in ring 1, at which point you are in deep shit anyway.
next prev parent reply other threads:[~2005-10-12 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 20:15 Jonathan M. McCune
2005-10-11 20:36 ` Brian Gerst
2005-10-11 20:24 ` Alon Bar-Lev
2005-10-11 21:12 ` Al Viro
2005-10-11 21:14 ` Brian Gerst
2005-10-12 9:05 ` Arjan van de Ven [this message]
2005-10-12 16:07 ` Alan Cox
2005-10-12 15:44 ` Arjan van de Ven
2005-10-12 23:55 ` Jonathan M. McCune
2005-10-12 13:03 ` linux-os (Dick Johnson)
2005-10-13 8:51 ` Denis Vlasenko
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=1129107936.3082.34.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=alon.barlev@gmail.com \
--cc=arvinds@cs.cmu.edu \
--cc=bgerst@didntduck.org \
--cc=jonmccune@cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=parno@cmu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®