`__stack_chk_fail' with 2.6.17.11

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

`__stack_chk_fail' with 2.6.17.11

Postby clem » Sat Feb 24, 2007 1:12 pm

Hello

I am trying to compile grsecurity-2.1.9-2.6.17.11-200609031316 and 2.6.17.11 on Debian. I am using an old version because I have an old app that doesn't seem to run on anything other than 2.6.17.11, I don't know why.

All I have set with regards to grsecurity is setting it to high, nothing else, and I am using the generic configuration from the grsecurity docs.

When compiling, I get the following error:

Code: Select all
init/built-in.o: In function 'try_name':
do_mounts.c.text+0x503): undefined reference to `__stack_chk_fail'
init/built-in.o: In function 'name_to_dev_t':
(.text+0x7eb): undefined reference to `__stack_chk_fail'
init/built-in.o: In function 'change_floppy':
(.init.text+0x9c1):undefined reference to `__stack_chk_fail'
init/built-in.o: In function 'mount_block_root':
(.init.text+0xc57):undefined reference to `__stack_chk_fail'
init/built-in.o: In function 'do_header':
initramfs.c.init.text+0x4323):undefined reference to `__stack_chk_fail'
arch/i386/kernel/built-in.o.text+0x5261):more undefined references to `__stack_chk_fail' follow
make[1]: *** [vmlinux] Error 1
make[1]: Leaving directory `/usr/src/linux-2.6.17.11'
make: *** [debian/stamp-build-kernel] Error 2

I have tried the workaround that someone else here posted:
Code: Select all
export CFLAGS="$CFLAGS -fno-stack-protector"

But it does not work.

Do anyone know how i can get this to compile?

Kind regards
clem
 
Posts: 1
Joined: Sat Feb 24, 2007 1:03 pm

Postby tosh » Sat Feb 24, 2007 10:50 pm

Try that way:
Code: Select all
make bzImage modules \
    CC="gcc -fno-stack-protector -fno-stack-protector-all"
tosh
 
Posts: 19
Joined: Mon Apr 10, 2006 9:13 pm

Re: `__stack_chk_fail' with 2.6.17.11

Postby PaX Team » Sat Mar 10, 2007 6:06 am

clem wrote:I am trying to compile grsecurity-2.1.9-2.6.17.11-200609031316 and 2.6.17.11 on Debian. I am using an old version because I have an old app that doesn't seem to run on anything other than 2.6.17.11, I don't know why.
that's interesting, normally linux folks take great care to preserve binary compatibility. you should report this to lkml along with some straces probably.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm


Return to grsecurity support