Re: [patch V4 2/8] mm/highmem: Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP

2020-11-19 Thread Linus Torvalds
On Thu, Nov 19, 2020 at 12:46 AM Mel Gorman wrote: > > And not start thinking it as a security hardening option. It's probably the reverse of a hardening option, since it will cause mapping of stuff in known and controllable virtual addresses. Although any kmap'able page is likely to already be

Re: [patch V4 2/8] mm/highmem: Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP

2020-11-19 Thread Mel Gorman
On Wed, Nov 18, 2020 at 01:13:57PM -0800, Linus Torvalds wrote: > On Wed, Nov 18, 2020 at 12:58 PM Thomas Gleixner wrote: > > > > Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP which forces the temporary > > mapping even for lowmem pages. This needs to be a seperate config switch > > because this only

Re: [patch V4 2/8] mm/highmem: Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP

2020-11-18 Thread Linus Torvalds
On Wed, Nov 18, 2020 at 12:58 PM Thomas Gleixner wrote: > > Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP which forces the temporary > mapping even for lowmem pages. This needs to be a seperate config switch > because this only works on architectures which do not have cache aliasing > problems. Very

[patch V4 2/8] mm/highmem: Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP

2020-11-18 Thread Thomas Gleixner
CONFIG_DEBUG_KMAP_LOCAL, which is selected by CONFIG_DEBUG_HIGHMEM is only providing guard pages, but does not provide a mechanism to enforce the usage of the kmap_local() infrastructure. Provide CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP which forces the temporary mapping even for lowmem pages. This