Hi,
btw: I'll have some x11-fb changes in the queue, so there will
be at least one more patchkit. The patch need some more work
though. I'll want to have the x11-fb patch ready for submit
soon, so I can push it mainline for 2.6.13.
Uploaded to
So, in practice, it's correct to call bad_segv() as done in the patch, but we
miss some cases. Only this time I've verified this well enough that I feel we
could merge your patch. However, I've not found any possible *realistic*
source of general protection faults. Especially I didn't find
On Tue, Mar 22, 2005 at 06:53:20PM +0100, Blaisorblade wrote:
On Sunday 20 March 2005 16:03, Gerd Knorr wrote:
1) how the user must choose what he wants (SUBARCH=i386 can be useful,
maybe a Kconfig option would be nice - we need to choose the default
depending on the host arch
No, this does not happen... the normal situation currently is that the kernel
skips printing part of the initial output.
$ ./OldKernels/vmlinux-2.6.11-rc3
Checking for /proc/mm...found
Checking for the skas3 patch in the host...found
Checking PROT_EXEC mmap in /tmp...OK
ject_hotplug -
