New warnings grsecurity-2.1.11-2.6.22.9-200709280630

[erikd]

I have ignored all the "warning: missing initializer" for some releases now but with 2.6.22.9 i get some warnings i havent seen before, the 'make bzImage' ends with:

Code: Select all

...
  SYSMAP  .tmp_System.map
  MODPOST vmlinux
WARNING: arch/i386/kernel/built-in.o(.exit.text+0x19): Section mismatch: reference to .init.text: (after 'cache_remove_dev')
WARNING: kernel/built-in.o(.text+0x1706c): Section mismatch: reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
  AS      arch/i386/boot/bootsect.o
  LD      arch/i386/boot/bootsect
  AS      arch/i386/boot/setup.o
  LD      arch/i386/boot/setup
  AS      arch/i386/boot/compressed/head.o
  CC      arch/i386/boot/compressed/misc.o
include/asm/processor.h: In function `native_get_debugreg':
include/asm/processor.h:536: warning: asm operand 0 probably doesn't match constraints
include/asm/processor.h: In function `native_set_debugreg':
include/asm/processor.h:563: warning: asm operand 0 probably doesn't match constraints
  OBJCOPY arch/i386/boot/compressed/vmlinux.bin
  GZIP    arch/i386/boot/compressed/vmlinux.bin.gz
  LD      arch/i386/boot/compressed/piggy.o
  LD      arch/i386/boot/compressed/vmlinux
  OBJCOPY arch/i386/boot/vmlinux.bin
  HOSTCC  arch/i386/boot/tools/build
  BUILD   arch/i386/boot/bzImage
Root device is (8, 0)
Boot sector 512 bytes.
Setup is 4922 bytes.
System is 2533 kB
Kernel: arch/i386/boot/bzImage is ready  (#1)

The kernel works but i dont really like to use it on a production server atm

[PaX Team]

I have ignored all the "warning: missing initializer" for some releases now but with 2.6.22.9 i get some warnings i havent seen before, the 'make bzImage' ends with:

if you mean the asm operand 0 message, i don't know why gcc is complaining, but we surely don't touch that code (the BUG macro in include/asm-i386/bug.h). do you get the same with the vanilla sources as well?

[erikd]

Ofc i should have tried compiling the vanilla kernel first (but in my defence -grsec _is_ vanilla for us ), the same problem occurs there so im sorry that iv bother you for nothing

I guess im back to patching the system a bit more, its an old installation that only have hade security fix upgrades and now im trying to get _everything_ up2date and also switching kernel 2.4->2.6
Just tried a basic slack12 installation and compiled vanilla 2.6.22.9 without problems.