On Tue, Mar 19, 2019 at 03:15:41PM +0000, Vincenzo Frascino wrote: > When kuser helpers are enabled the kernel maps the relative code at > a fixed address (0xffff0000). Making configurable the option to disable > them means that the kernel can remove this mapping and any access to > this memory area results in a sigfault. > > Add a KUSER_HELPERS config option that can be used to disable the > mapping when it is turned off. > > This option can be turned off if and only if the applications are > designed specifically for the platform and they do not make use of the > kuser helpers code. > > Note: kuser helpers is disabled by default with 64K pages. Actually this last sentence is more than just the default y/n for this option. It adds a hard dependency, which means it cannot be enabled. Currently we do allow COMPAT with 64K pages if EXPERT. Is the main reason for this just to be able to subtract PAGE_SIZE for TASK_SIZE_32 in the last patch? What happens if we leave TASK_SIZE_32 set to 0x100000000 for the 64K page configuration? Do we still have the C99 issue mentioned in the cover letter (assuming that the last page is already occupied by the vectors page)? -- Catalin
