linux-kernel - Re: [RFC] enhancing the kernel's graphics subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <21d7e9970705210227x27234e2dme4e731a53f977082@mail.gmail.com>
Date:	Mon, 21 May 2007 19:27:49 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Helge Hafting" <helge.hafting@...el.hist.no>
Cc:	"Jon Smirl" <jonsmirl@...izon.net>,
	"Jesse Barnes" <jesse.barnes@...el.com>, jonsmirl@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

On 5/21/07, Helge Hafting <helge.hafting@...el.hist.no> wrote:
> Dave Airlie wrote:
> > On 5/21/07, Jon Smirl <jonsmirl@...izon.net> wrote:
> >> On Thu, 17 May 2007 14:23:45 -0700, Jesse Barnes wrote:
> >>
> >> > In collaboration with the FB guys, we've been working on enhancing the
> >> > kernel's graphics subsystem in an attempt to bring some sanity to the
> >> > Linux graphics world and avoid the situation we have now where several
> >> > kernel and userspace drivers compete for control of graphics devices.
> >>
> >> How is supporting different users logged into each head going to work?
> >> The original model for this was to give each head its own fbdev device.
> >> It is important that each user be able to set their own mode without
> >> being
> >> root.
> >
> > TThe problem with that is the concept of heads is flawed... there is
> > in reality no such
> > thing, you have crtcs and outputs, no heads. So any attempt to enforce
> > the head concept involves putting policy into the kernel, as if I have
> > 3 outputs but 2 crtcs how do I decide the mappings without the admin
> > telling the kernel,
> >
> Solution:
> One device per crtc. You can then have two users, running consoles
> or xservers on their crtcs, without having to involve root.

Thats pretty much what the code does, but you still are putting a
certain amount of policy in the kernel...
>
> The crtc->output mapping must still be done by root of course.
>
> This solution allow the useful case where the computer boots, the boot
> scripts
> set up a crtc->output mapping. Then users log in through the
> various consoles (using getty or xdm or similiar) using their grahphical
> devices in whatever way they want.  A true multiseat setup.
>
>
> And if one user needs to use all the screens for multi-display work?
> Let root change the mappings, possibly through some sudo setup.
>

Multiseat isn't what i would want as a default on any machine, so the
default setup should be to clone the single user onto as many screens
as possible, as this is what users expect.. the system startup scripts
can then reconfigure it, to suit the admins needs..

Dave.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/