Slab corruption: start=0922713c, len=512
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<080b57ba>](free_pipe_info+0x3e/0x58)
160: 00 4e 68 08 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=09227348, len=512
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<080b57f2>](pipe_new+0x1e/0x64)
000: 18 10 17
I've been seeing MM red zone messages on 2.6.16-fc3 with Jeff's patchset
from a couple of weeks ago. I haven't reported them since that's a
pretty old version by now. Should I post the next bunch I see?
-- John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTE
Title: Unknown symbol vsyscall_end when loading external module
I'm getting this when loading an externally built module:
infinity: Unknown symbol vsyscall_end
infinity: Unknown symbol vsyscall_ehdr
The module uses copy_from_user(). When ARCH=um, copy_from_user() is defined as inline, a
Title: Build error in arch/um/os-Linux/aio.c with today's 2.6.16-rc4 patch set
It appears to me that the kernel tree will not build with the 2.6.16-rc4 patch set I downloaded today, if HAVE_AIO_ABI is not defined.
finish_aio_26() is referenced in arch/um/os-Linux/aio.c, but is not defined.
