mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Dave Airlie" <airlied@gmail.com>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	"Ed White" <ed.white@libero.it>,
	ML <linux-kernel@vger.kernel.org>
Subject: Re: SecurityFocus Article
Date: Fri, 12 May 2006 01:07:13 -0400	[thread overview]
Message-ID: <9e4733910605112207t3e20218akc7b697987c47059b@mail.gmail.com> (raw)
In-Reply-To: <21d7e9970605112113s16764073tca5246d1e104503b@mail.gmail.com>

On 5/12/06, Dave Airlie <airlied@gmail.com> wrote:
> Your ideas to fix X didn't result in patches to fix X, ideas are great
> we all have ideas, patches are better, for some reason we don't all
> have patches. We are fixing X, you are not.

In the past I wasted way too much time writing patches for X. I
understand now that there is little consensus on where X is going in
the future. X has few resources and many of these resources work at
cross purposes. You are doing a fine job, please keep up the good
work. For my part I have chosen to stop working in such a chaotic
environment.

But, no matter how you slice it, X is still a multi-megabyte process
needlessly running as root which makes it a scary security issue. I
know you are already aware of the philosophical and architectural
changes needed to switch X to a model where it runs as a normal
process and relies on the kernel for privileged operations. You and
Ian are taking the first steps, I hope that X will reach the consensus
necessary to implement the full change.

Question my sanity if you want, but I'm sticking with the old fashion
idea that privileged code that mucks with hardware belongs in a device
driver. I'm also stuck on the radical idea that only one device driver
at a time should be in control of a piece of hardware. X violates both
of these.

-- 
Jon Smirl
jonsmirl@gmail.com

      reply	other threads:[~2006-05-12  5:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 14:34 Ed White
2006-05-11 15:06 ` Andi Kleen
2006-05-11 15:32 ` Alan Cox
2006-05-11 15:47 ` linux-os (Dick Johnson)
2006-05-11 20:03   ` Ingo Oeser
2006-05-12  0:19   ` Segher Boessenkool
2006-05-12  3:17   ` Jon Smirl
2006-05-12  4:13     ` Dave Airlie
2006-05-12  5:07       ` Jon Smirl [this message]

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=9e4733910605112207t3e20218akc7b697987c47059b@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=airlied@gmail.com \
    --cc=ed.white@libero.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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®