linux-kernel - Re: console font limits

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:	Thu, 3 May 2007 11:20:23 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Albert Cahalan <acahalan@...il.com>,
	"Antonino A. Daplas" <adaplas@...il.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	linux-kernel <linux-kernel@...r.kernel.org>, aeb@....nl
Subject: Re: console font limits

On Thu, 03 May 2007 00:19:59 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> Albert Cahalan wrote:
> > Font size is not a sane place to draw the line. Features are.
> 
> Font sizes are an eminently sane place to draw the line, because the
> crossover is largely determined by the point at which nailing down too
> much memory (kernel memory = unswappable memory) gets too expensive.

Which is a value judgement made based upon the cost of memory, the
memory limit of the system (and the fixed kmalloc limits).

Obvious fix Albert would be to post patches which 

	-	Ignore the font size limits (up to sanity point) for 
		CAP_SYS_something
	-	Put the limit in sysfs where it belongs
	-	Use vmalloc not kmalloc if neccessary

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/