pax-linux-2.6.27.3-test8 build error on 32bit

[cormander]

Code: Select all

HOSTLD  scripts/mod/modpost
  CC      kernel/bounds.s
  GEN     include/linux/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
In file included from arch/x86/kernel/asm-offsets.c:2:
arch/x86/kernel/asm-offsets_32.c: In function âfooâ:
arch/x86/kernel/asm-offsets_32.c:117: error: invalid use of undefined type âstruct pv_cpu_opmâ
make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2


This is when CONFIG_XEN=y

I don't have this problem on 64bit

[PaX Team]

arch/x86/kernel/asm-offsets_32.c:117: error: invalid use of undefined type struct pv_cpu_opm

oops, a typo, that should be _ops not _opm. any other problems?

[tjh]

It wouldn't boot for me, it crashed somewhere before it tried to mount root.

I realise this is a terrible, terrible error report.

I can try and copy down the oops if you wish tomorrow morning.

Is there any easy way to get the oops from the screen logged somewhere as it crashes, before boot?

I can attach my .config as well if that helps.

Tim

[PaX Team]

I can try and copy down the oops if you wish tomorrow morning.

Is there any easy way to get the oops from the screen logged somewhere as it crashes, before boot?

i'd definitely need any details you can get from the crash, preferably some screenshot (of a framebuffer console if possible) or netconsole log of the oops itself, with kernel symbols enabled.

I can attach my .config as well if that helps.

this would be helpful mostly if this kernel can boot (and fail) under qemu as well, otherwise the oops report is more important for now.

[tjh]

I copied the first few lines by hand. This is actually the second oops to go up the screen as well, I can't get the first one, no matter how I set my console it's not big enough. The screen won't scroll back either...

If these don't help let me know and I'll try a netconsole.

Code: Select all

PAX: modprobe:389, uid/euid: 0/0 attempted to modify kernel code
BUG: Ubale to handle kernel paging request c0600314
[P: [<000561d6> map_vm_area+0x153/0x160


[PaX Team]

Code: Select all

PAX: modprobe:389, uid/euid: 0/0 attempted to modify kernel code
BUG: Ubale to handle kernel paging request c0600314
[P: [<000561d6> map_vm_area+0x153/0x160


ok, this gives me some idea already, can you copy the rest of the stack backtrace as well please? do you happen to know which module is loading at this point? in any case, once this is fixed (try -test10 please), we'll look at the first oops as well (if it's got a different cause).

[tjh]

I have been away for a few days, I just tried the latest grsec patch that appeared today -> grsecurity-2.1.12-2.6.27.4-200810272314.patch
Still doesn't work for me, here's as much as I copied down before the screen went blank and I couldn't revive it!!

I *did* try netconsole, it happily logs, but none of the crash. It's really odd.

Anyway:
(This is all typed in by hand, so there's probably errors!)

Code: Select all

INIT: version 2.86 booting
PAX modprobe:399, uid/euid:0/0, attempted to modify kernel code
BUG: unable to handle kernel paging request at c065c000
IP: [<001e2678>]
*pdpt = 0000000000657001 *pde = 00000000006001e1
Ooops: 00003 [#1] SMP
Module Linked in:

Pid: 399, comm: modprobe Tained: G          W (2.6.27.4-grsec #3)
EIP: 0060:[<001e2678>] EFLAGS: 00010246 CPU: 0
EAX: 00000000 EBX: 00006ed7 ECX: 00006ed7 EDX: 00000003
ESI: a465c000 EDI: c065c000 EBP: f704e000 ESP: f704eea4
 DS: 007b ES: 0068 FS: 00d8 GS: 0033 SS: 0068
Process modprobe (pid: 399, ti=f704e000 task=f7b51810 task.ti=f704e000)


This was the only thing that logged this time around, it appears to be a little different. Maybe because I compiled in the VESA Framebuffer driver to get more data on the screen.

Let me know if you need me to attach the config.

[PaX Team]

(This is all typed in by hand, so there's probably errors!)

thanks, a digital camera shot also works btw .

Let me know if you need me to attach the config.

please email me the System.map corresponding to this kernel instead so that i can resolve all the addresses (or if you know how to do it, find out what is at/around c065c000 and 001e2678).

[tjh]

Have emailed you some details which I hope help!

[PaX Team]

Have emailed you some details which I hope help!

-test12 should fix it.