linux-kernel - Re: [PATCH] lib: move kasprintf to a separate file

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]

Date:	Sun, 29 Jul 2007 22:08:00 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Meelis Roos <mroos@...ux.ee>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Richard Henderson <rth@...ddle.net>,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Jay Estabrook <jay.estabrook@...com>
Subject: Re: [PATCH] lib: move kasprintf to a separate file

On Sat, Jul 28, 2007 at 03:48:32PM -0700, Jeremy Fitzhardinge wrote:
> Sam Ravnborg wrote:
> > kasprintf pulls in kmalloc which proved to be fatal for at least
> > bootimage target on alpha.
> > Move it to a separate file so only users of kasprintf are exposed
> > to the dependency on kmalloc.
> >   
> 
> OK by me (that's what my original patch did), but it might be worth
> documenting what environmental constraints vsprintf.c is under.  I
> didn't realize it was used by non-kernel code.

Looking for other users I saw that i386 iboot had included a minimal printf
implmentation which could also be a possibility for alpha.
Now the i386 printf does not support 64 bit - but I dunno if this is
a problem for alpha.

Actually I would prefer the local printf solution for alpha to
keep dependencies on the functions in lib/ as one may expect 
them (kernel only - not boot).

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