linux-kernel - Re: [PATCH] Add possibility to set /dev/tty number

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]

Date:	Wed, 6 Jan 2016 13:54:39 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	"Austin S. Hemmelgarn" <ahferroin7@...il.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Pierre Paul MINGOT <mingot.pierre@...il.com>, jslaby@...e.cz,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add possibility to set /dev/tty number

> In fact, there already appears to be some degree of allocation on demand 
> for VT's (otherwise deallocvt has no point), just not for everything 
> associated with the VT.  I'd be willing to bet that almost everything 
> that reasonably can be dynamically allocated already is, there is a bare 
> minimum required for even a virtual device after all.

If there is 1.6K overhead per vt coming from somewhere (given we only
preallocate 1 VT) then either

- There is stuff not being dynamically allocated (which you can find and
  fix)

- Your userspace is triggering those dynamic allocations

There is no magic thing that requires 1.6K of kernel data per console.

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/