> I thought Mozilla also used the low bits of pointers for special cases Effectively, all code that has to deal with the underlying details of the function pointer implementation is affected. This includes unwind code, and code to dynamically load libraries and plugins. > ... and the kernel even has macros to return 'either a pointer or an > error code' (PTR_ERR, ERR_PTR, IS_ERR). Although the kernel probably > wouldn't trip this, as I can't think of any function which returns a > function-pointer-or-error (and besides the test isn't 'are the bottom > bits set', but 'if you cast this pointer back to an unsigned long, is it > greater than -4095'. The PLABEL bit is defined in the runtime and only affects the runtime. I think the only time the kernel would need to care about this is for signal handlers. In the runtime, page 0 is reserved to catch invalid pointer accesses. I'm sure the kernel has to be aware of this. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
