linux-kernel - Re: [PATCH] Add a new VT mode which is like VT_PROCESS but doesn't require a VT

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] [day] [month] [year] [list]

Message-ID: <20100219120730.4793ce0d@lxorguk.ukuu.org.uk>
Date:	Fri, 19 Feb 2010 12:07:30 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Ari G. Entlich" <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

> 1. VT_AUTO doesn't send signals to anything when a VT switch happens, precisely
>    because VT_AUTO is supposed to be used in the case where there's nothing to
>    send signals TO (i.e. the VT is managed by the kernel). The X server still
>    needs to know about VT switches to turn input devices off and such.

Ok..

> VT_ACKACQ, it wouldn't really make sense for there to be a new VT_ACKACQ value,
> because VT_ACKACQ is something which gets passed to a VT_RELDISP, and VT_RELDISP
> isn't needed at all in this new mode.

I don't want to change the existing values as they are somewhat visible
to user space.

> I hope that clarifies things.

Yes. You could use the VT_EVENT facility for the switch monitoring but
the asynchronous nature of the reporting probably isn't what is needed
for input device switching etc.

Looks fine to me - just bump the value and resubmit
--
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/