linux-kernel - Re: Fw: Re: 2.6.18-rc5-mm1 + all hotfixes -- BUG: MAX_STACK_TRACE

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>] [day] [month] [year] [list]

Message-ID: <a44ae5cd0609031429x30c74a80l2399f0abf2f1c1a7@mail.gmail.com>
Date:	Sun, 3 Sep 2006 14:29:42 -0700
From:	"Miles Lane" <miles.lane@...il.com>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Fw: Re: 2.6.18-rc5-mm1 + all hotfixes -- BUG: MAX_STACK_TRACE_ENTRIES too low!

On 9/3/06, Sam Ravnborg <sam@...nborg.org> wrote:
> On Sun, Sep 03, 2006 at 02:16:05PM -0700, Miles Lane wrote:
> > On 9/3/06, Sam Ravnborg <sam@...nborg.org> wrote:
> > >
> > >[ketchup -g 2.6-mm; make defconfig; make menuconfig]
> > >
> > >[sam@...tun mm]$ grep LOCKDEP .config
> > >CONFIG_LOCKDEP_SUPPORT=y
> > >CONFIG_LOCKDEP=y
> > >CONFIG_DEBUG_LOCKDEP=y
> > >[sam@...tun mm]$ make
> > >  CHK     include/linux/version.h
> > >  CHK     include/linux/utsrelease.h
> > >  CHK     include/linux/compile.h
> > >  MODPOST vmlinux
> > >Kernel: arch/i386/boot/bzImage is ready  (#3)
> > >  Building modules, stage 2.
> > >  MODPOST 1 modules
> > >[sam@...tun mm]$ touch kernel/lockdep_internals.h
> > >[sam@...tun mm]$ make
> > >  CHK     include/linux/version.h
> > >  CHK     include/linux/utsrelease.h
> > >  CHK     include/linux/compile.h
> > >  CC      kernel/lockdep.o
> > >  CC      kernel/lockdep_proc.o
> > >
> > >Works for me?
> > >
> > >Miles - can you double check that you have CONFIG_LOCKDEP defined.
> >
> > Ah, I suspect I was being a dufus.  I was looking for the exact
> > filename, since I rarely receive patches for anything other than C
> > files.  I probably overlooked it.  I'm very sorry to have bothered
> > you.  BTW, yes, I had it defined.
>
> No problem.
> Can I request you to do a follow-up post to the mail at lkml
> just so people do not start to mistrust kbuild.
>
> It takes quiet some time to gain trust but only little to loose
> it again so it would be very nice to close this one in public.

Sure.  I didn't notice you had dropped LKML off the CC list in your reply.

Hey everyone, mea culpa.  KBuild is working fine!  :-)

-- 
VGER BF report: U 0.500013
-
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/