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, 19 Jan 2009 15:09:22 -0200
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
Cc:	Sam Ravnborg <sam@...nborg.org>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kmemtrace: kbuild failed to make the new header symlink...

Em Mon, Jan 19, 2009 at 06:59:26PM +0200, Eduard - Gabriel Munteanu escreveu:
> On Mon, Jan 19, 2009 at 02:40:29PM -0200, Arnaldo Carvalho de Melo wrote:
> > Sam,
> > 
> > 	I just did a git pull on linux-2.6-tip, then, on a build
> > directory (make O=../build/blkftrace/) with a previous build a tree
> > cloned from Linus I got stuck with the messages below.
> > 
> > 	I could only get this to work after a make mrproper, thought I
> > could mention this so that perhaps this can get detected and time be
> > saved somehow.
> > 
> >   CC      arch/x86/mm/fault.o
> > /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:38:27: error: asm/kmemcheck.h: No such file or directory
> > /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c: In function ???do_page_fault???:
> > /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:614: error: implicit declaration of function ???kmemcheck_active???
> > /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:615: error: implicit declaration of function ???kmemcheck_hide???
> > /home/acme_unencrypted/git/linux-2.6-tip/arch/x86/mm/fault.c:644: error: implicit declaration of function ???kmemcheck_fault???
> 
> Hi,
> 
> This looks like a kmemcheck, not kmemtrace, fault. Heh, but we already
> have 3 things with similar names: kmemcheck, kmemtrace and kmemleak. :)

Yeah, sorry for that, but the problem in the end, seems to be in kbuild,
not in any of those kmemFEATURES :)

Anyway, when in doubt, use Mr. Proper products and go on with life :-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ