[lkml]   [2003]   [Jan]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] extable cleanup

On Fri, 3 Jan 2003, Rusty Russell wrote:
> Fairly straightforward consolidation of extable handling. Sparc64 is
> trickiest, with its extable range stuff (ideally, the ranges would be
> in a separate __extable_range section, then the extable walking code
> could be made common, too).
> Only tested on x86: ppc and sparc64 written untested, others broken.

Did you test on a true i386, which needs exception handling very early on
to handle the test for broken WP? In other words, are all the exception
table data structures properly initialized?

And did you check that an oops in the init handling works correctly before
the kallsyms table has been initialized? That "initcall(symbol_init)"
makes me suspect it won't..

There was a reason why "extable_init()" was in init/main.c, and was done


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.047 / U:1.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site