linux-kernel - Re: [PATCH] VT: Add a boot option to disable cursor on boot

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: <20090904161507.GA24697@srcf.ucam.org>
Date:	Fri, 4 Sep 2009 17:15:07 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] VT: Add a boot option to disable cursor on boot

On Fri, Sep 04, 2009 at 06:03:02PM +0100, Alan Cox wrote:

> Seems odd to me - why can't the splash screen app in initrd just issue
> the call to turn off the cursor - or is this splash screen coming from
> something else ?

The kernel unconditionally enables the cursor before any userspace has 
run, even if we've turned it off in the bootloader. That's the window 
I'm trying to close.

> - If the splash screen is kernel based then the splash screen module
>   needs to be able to ask the vt driver itself
> - If not then the user space can use ioctls like everyone else (see
>   setterm)

(see above)

> - It should be implemented without adding an extra condition to a pile of
>   ifs (or the condition mess at least become a single cursor_visible_p())

It doesn't add or alter any conditionals in its current form?

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/