Problem with 2.6.23.12

Discuss and suggest new grsecurity features

Problem with 2.6.23.12

Postby hackman » Thu Jan 10, 2008 4:33 am

Hello,
I'm trying to apply grsecurity-2.1.11-2.6.23.9-200712101800.patch to a 2.6.23.12 kernel.
But after the build, the bzImage is not created and I see these errors:

CHK include/linux/version.h
CHK include/linux/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
LD arch/i386/boot/setup.elf
OBJCOPY arch/i386/boot/compressed/vmlinux.bin
/bin/sh: line 1: 7879 File size limit exceededobjcopy -O binary -R .note -R .comment -S vmlinux arch/i386/boot/compressed/vmlinux.bin
make[2]: *** [arch/i386/boot/compressed/vmlinux.bin] Error 153
make[1]: *** [arch/i386/boot/compressed/vmlinux] Error 2
make: *** [bzImage] Error 2

Even if I only patch the sources without enabling any grsec/pax options I see the same errors.

can anyone give me a hint?
hackman
 
Posts: 10
Joined: Mon Jan 07, 2008 4:46 am

Re: Problem with 2.6.23.12

Postby hackman » Thu Jan 10, 2008 9:14 am

I hope that this will help in resolving the issue, I saw these warnings:

WARNING: vmlinux.o(.text+0xe722): Section mismatch: reference to .init.data:efi_bak_pg_dir_pointer (between 'efi_call_phys_prelog' and 'efi_call_phys_epilog')
WARNING: vmlinux.o(.text+0xe72c): Section mismatch: reference to .init.data: (between 'efi_call_phys_prelog' and 'efi_call_phys_epilog')
WARNING: vmlinux.o(.text+0xe797): Section mismatch: reference to .init.data:efi_bak_pg_dir_pointer (between 'efi_call_phys_epilog' and 'efi_set_rtc_mmss')
WARNING: vmlinux.o(.text+0xe7a1): Section mismatch: reference to .init.data: (between 'efi_call_phys_epilog' and 'efi_set_rtc_mmss')
WARNING: vmlinux.o(.text+0xe841): Section mismatch: reference to .init.text:phys_efi_get_time (between 'efi_get_time' and 'is_available_memory')
hackman
 
Posts: 10
Joined: Mon Jan 07, 2008 4:46 am

Re: Problem with 2.6.23.12

Postby hackman » Thu Jan 10, 2008 9:49 am

I'm sorry, I remembered that I had the same problem a year ago.

The problem was old version of binutils. I upgraded to 2.18 and now everything is fine.

This forum is a great source of information.
hackman
 
Posts: 10
Joined: Mon Jan 07, 2008 4:46 am

Re: Problem with 2.6.23.12

Postby PaX Team » Sun Jan 13, 2008 10:08 am

hackman wrote:The problem was old version of binutils. I upgraded to 2.18 and now everything is fine.
just for a reference for others, which binutils version didn't work?
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Re: Problem with 2.6.23.12

Postby hackman » Mon Jan 14, 2008 2:42 pm

binutils-2.15.92.0.2-24 (RHEL4)
I installed 2.18 from source and removed 2.15
hackman
 
Posts: 10
Joined: Mon Jan 07, 2008 4:46 am

Re: Problem with 2.6.23.12

Postby btnet » Fri Feb 01, 2008 3:58 am

i had the same problem with the same versions, upgrade helped me.
the default rhel4 binutils won't let the kernel to compile.
btnet
 
Posts: 21
Joined: Tue Jan 29, 2008 12:59 pm

Re: Problem with 2.6.23.12

Postby fed.linuxgossip » Mon Feb 25, 2008 9:51 am

Hi folks,

I am facing the same problem, can you please list the steps to upgrade binutils from source and remove the rpm install. I want to be extra-cautious before doing it myself on a live server.

FYI,

[root@server ~]# cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
[root@server ~]#


[root@server ~]# rpm -q binutils
binutils-2.15.92.0.2-24
[root@server ~]#


[root@server~]# up2date -v --nox binutils

Fetching Obsoletes list for channel: rhel-i386-es-4...

Fetching rpm headers...

Name Version Rel
----------------------------------------------------------

The following packages you requested are already updated:
binutils
[root@server ~]#


Thanks
Last edited by fed.linuxgossip on Tue Feb 26, 2008 12:34 am, edited 1 time in total.
fed.linuxgossip
 
Posts: 21
Joined: Mon Feb 25, 2008 9:46 am

Re: Problem with 2.6.23.12

Postby PaX Team » Sun Mar 02, 2008 5:22 am

hackman wrote:I hope that this will help in resolving the issue, I saw these warnings:

WARNING: vmlinux.o(.text+0xe722): Section mismatch: reference to .init.data:efi_bak_pg_dir_pointer (between 'efi_call_phys_prelog' and 'efi_call_phys_epilog')
WARNING: vmlinux.o(.text+0xe72c): Section mismatch: reference to .init.data: (between 'efi_call_phys_prelog' and 'efi_call_phys_epilog')
WARNING: vmlinux.o(.text+0xe797): Section mismatch: reference to .init.data:efi_bak_pg_dir_pointer (between 'efi_call_phys_epilog' and 'efi_set_rtc_mmss')
WARNING: vmlinux.o(.text+0xe7a1): Section mismatch: reference to .init.data: (between 'efi_call_phys_epilog' and 'efi_set_rtc_mmss')
WARNING: vmlinux.o(.text+0xe841): Section mismatch: reference to .init.text:phys_efi_get_time (between 'efi_get_time' and 'is_available_memory')
i forgot about this, fixed in test33. are you actually booting with EFI? if yes, does it work even in PAE mode?
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm


Return to grsecurity development