linux-kernel - Re: [PATCH] kmemtrace: fix build breakage in befs

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:	Tue, 24 Mar 2009 10:31:03 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	eduard.munteanu@...ux360.ro, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kmemtrace: fix build breakage in befs


* Pekka Enberg <penberg@...helsinki.fi> wrote:

> On Tue, 2009-03-24 at 10:17 +0100, Ingo Molnar wrote:
> > > OK, I think all of them are now fixed. I haven't yet been able to 
> > > complete a build so help is still appreciated. ;-)
> > 
> > unless there's a mail delay, we still have:
> > 
> > lib/decompress_unlzma.c:122: error: implicit declaration of function ‘kfree’
> > lib/decompress_unlzma.c:551: error: implicit declaration of function ‘kmalloc’
> 
> Sorry, I missed that. I was testing the .config you sent in the 
> initial mail, not allyesconfig. I sent you a patch to fix that as 
> well now.

no problem, i missed it too - computer reminded us that it's still 
there ;-)

there's a new headers-export-check failure:

/home/mingo/tip/usr/include/linux/bsg.h:11: found __[us]{8,16,32,64} type without #include <linux/types.h>
/home/mingo/tip/usr/include/linux/fs.h:11: included file 'linux/gfp.h' is not exported
make[3]: *** [/home/mingo/tip/usr/include/linux/.check] Error 1
make[2]: *** [linux] Error 2

(CONFIG_HEADERS_CHECK)

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