linux-kernel - Re: [PATCH] fonts:Kconfig: fix default enable FONT_8x8 and FONT

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:	Mon, 30 Dec 2013 14:48:42 +0800
From:	Wang YanQing <udknight@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	jslaby@...e.cz, airlied@...hat.com, akpm@...ux-foundation.org,
	kilobyte@...band.pl, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fonts:Kconfig: fix default enable FONT_8x8 and FONT_8x16
 at the same time

On Sun, Dec 29, 2013 at 09:34:30PM -0800, Greg KH wrote:
> On Mon, Dec 30, 2013 at 11:37:45AM +0800, Wang YanQing wrote:
> > FONT_8x8 and FONT_8x16 have the same default value line:
> > "default y if !SPARC && !FONTS"
> > 
> > I test run "make defconfig" for x86 will enable FONT_8x8 and FONT_8x16 at
> > the same time.
> > 
> > This patch fix it, because FONT_AUTOSELECT choice FONT_8x16, so
> > I decide to disable FONT_8x8, this patch will reduce size of kernel.
> > 
> > Signed-off-by: Wang YanQing <udknight@...il.com>
> > ---
> >  lib/fonts/Kconfig | 1 -
> >  1 file changed, 1 deletion(-)
> 
> I am not the maintainer of this file, sorry.  Also, I don't think it's
> correct, if you want, you can always disable this option on your own.
> 
Hi Greg KH.

Sorry for confusion, the default behavior enable FONT_8x8 and FONT_8x16,
FONT_8x8 eat ~50KB memory, but kernel never use it. I think this is not
good default behavior.

Thanks.
--
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/