| 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
| ||
|
Date: Fri, 19 Feb 2010 10:46:16 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: atrigent@....neu.edu Cc: linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH] Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call > If the X server eventually uses this new mode, debugging and crash > recovery should become easier. This is because even when currently in > the VT of a frozen X server it would still be possible to switch out > by doing SysRq-r and then CTRL-<number of a text vt>, sshing in and > doing chvt <number of a text vt>, or any other method of VT switching. > The general concensus on #xorg-devel seems to be that it should be > safe to use this with X now that we have KMS. > > Signed-off-by: Ari Entlich <atrigent@....neu.edu> If KMS doesn't need to mode switch then does it need any of this stuff - can it not just switch to a console and use it ? Otherwise please use a different value than ACKACQ (just for clarity) and conceptually it looks fine to me - I just question if it's really needed as KMS based X not having to play with magic locking stuff would be cleaner still. Alan -- 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/
Powered by blists - more mailing lists