linux-kernel - Re: tty: add 'active' sysfs attribute to tty0 and console device

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 for Android: free password hash cracker in your pocket

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

Message-ID: <AANLkTinXy3pNhwqo5aqHrH9fN99JhJrBtnbbpnq2h_K-@mail.gmail.com>
Date:	Tue, 16 Nov 2010 21:15:32 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>,
	Lennart Poettering <lennart@...ttering.net>,
	Werner Fink <werner@...e.de>, Jiri Slaby <jslaby@...e.cz>
Subject: Re: tty: add 'active' sysfs attribute to tty0 and console device

On Tue, Nov 16, 2010 at 20:55, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>> we always will apply the final result just fine, when stuff stops
>> changing. It's actually a nice feature and no a problem at all, that
>> we only see the most recent state.
>
> Stuff never stops changing until the machine shuts down, its undefined.

Either you don't, or you just don't want to understand what all this
is about. :)

>> Sure, with the ioctl() we've seen many not interesting changes, but we
>> often miss the single one that is important -- the last last one. The
>> thing is that we don't need to sleep here and miss changes.
>
> So we fix the ioctl interface, it's not exactly hard to do now is it.
>
>> It's a straight-forward and simple text interface that does all we
>> need to track console and vt changes.
>
> Except that it doesn't address things like the permissions side of things.
>
> NAK again

Specifics please.

> "We have an interface that doesn't quite work for our case and we think
> that is a bug" is not the reasoning behind writing a new random one with
> a totally disconnected permission model that doesn't work either.
>
> Fix the one we have.

So how do you think you'll fix it? I better don't get into your
ioctl() business.

Kay
--
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/