summaryrefslogtreecommitdiff
path: root/arch/um/os-Linux/sys-i386/registers.c
diff options
context:
space:
mode:
authorJeff Dike <jdike@addtoit.com>2005-05-01 15:58:53 (GMT)
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-05-01 15:58:53 (GMT)
commit92eac95287d75f220a8bbef6646f51a6497c4b4c (patch)
tree487b3501d9f212cd3f763ee9d8c457b0cda28d56 /arch/um/os-Linux/sys-i386/registers.c
parent31df7b7fc6182b6c4e5c3b77084d0c026b3ac613 (diff)
downloadlinux-92eac95287d75f220a8bbef6646f51a6497c4b4c.tar.xz
[PATCH] uml: fix oops related to exception table
Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it> Prevent the kernel from oopsing during the extable sorting, as it can do now, because the extable is in the readonly section of the binary. Jeff says: The exception table turned RO in 2.6.11-rc3-mm1 for some reason. Moving it causes it to land in the writable data section of the binary. Paolo says: This patch fixes a oops on startup, which can be easily triggered by compiling with CONFIG_MODE_TT disabled, and STATIC_LINK either disabled or enabled. The resulting kernel will always Oops on startup, after printing this simple output: I've verified, by binary search on the BitKeeper repository (synced up as of 2.6.12-rc2), starting from the range 2.6.11-2.6.12-rc1, that this bug shows up on BitKeeper revisions in the range [@1.1994.11.168,+inf), i.e. starting from this: [PATCH] lib/sort: Replace insertion sort in exception tables Since UML does not use the exception table, it's likely that insertion sort didn't happen to write anything on the table. Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/um/os-Linux/sys-i386/registers.c')
0 files changed, 0 insertions, 0 deletions