Lift memcpy_[to|from]_page to core
Subsystems (6)
v2 cover Lift memcpy_[to|from]_page to core
From: Ira Weiny <[email protected]>
These are based on tip/core/mm. As I was looking at converting the calls to kmap_local_page() I realized that there were a number of calls in highmem.h which should also be converted.
So I've added a second prelim patch to convert those.
This is a V2 to get into 5.11 so that we can start to convert all the various subsystems in 5.12.[1]
I'm sending to Andrew and Thomas but I'm expecting these to go through tip/core/mm via Thomas if that is ok with Andrew.
[1] https://lore.kernel.org/lkml/[email protected]/
Ira Weiny (2):
mm/highmem: Remove deprecated kmap_atomic
mm/highmem: Lift memcpy_[to|from]_page to core
include/linux/highmem.h | 28 +++++++++++++------------- include/linux/pagemap.h | 44 +++++++++++++++++++++++++++++++++++++++++ lib/iov_iter.c | 26 +++--------------------- 3 files changed, 61 insertions(+), 37 deletions(-)
Signature · 1 line
2.28.0.rc0.12.gb6a658bd00c9
PATCH v2 1/2 mm/highmem: Remove deprecated kmap_atomic
From: Ira Weiny <[email protected]>
kmap_atomic() is being deprecated in favor of kmap_local_page().
Replace the uses of kmap_atomic() within the highmem code.
--- include/linux/highmem.h | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-)
include/linux/highmem.h +14 -14
@@ -146,9 +146,9 @@ static inline void invalidate_kernel_vmap_range(void *vaddr, int size)#ifndef clear_user_highpagestatic inline void clear_user_highpage (struct page *page,unsigned long vaddr) { -void *addr =kmap_atomic (page); +void *addr =kmap_local_page (page);clear_user_page (addr, vaddr, page); -kunmap_atomic (addr); +kunmap_local (addr); }#endif
@@ -199,16 +199,16 @@ alloc_zeroed_user_highpage_movable(struct vm_area_struct *vma,static inline void clear_highpage (struct page *page) { -void *kaddr =kmap_atomic (page); +void *kaddr =kmap_local_page (page);clear_page (kaddr); -kunmap_atomic (kaddr); +kunmap_local (kaddr); }static inline void zero_user_segments (struct page *page,unsigned start1,unsigned end1,unsigned start2,unsigned end2) { -void *kaddr =kmap_atomic (page); +void *kaddr =kmap_local_page (page);BUG_ON (end1 >PAGE_SIZE || end2 >PAGE_SIZE );
@@ -218,7 +218,7 @@ static inline void zero_user_segments(struct page *page,if (end2 > start2)memset (kaddr + start2,0 , end2 - start2); -kunmap_atomic (kaddr); +kunmap_local (kaddr);flush_dcache_page (page); }
@@ -241,11 +241,11 @@ static inline void copy_user_highpage(struct page *to, struct page *from, {char *vfrom, *vto; - vfrom =kmap_atomic (from); - vto =kmap_atomic (to); + vfrom =kmap_local_page (from); + vto =kmap_local_page (to);copy_user_page (vto, vfrom, vaddr, to); -kunmap_atomic (vto); -kunmap_atomic (vfrom); +kunmap_local (vto); +kunmap_local (vfrom); }#endif
@@ -256,11 +256,11 @@ static inline void copy_highpage(struct page *to, struct page *from) {char *vfrom, *vto; - vfrom =kmap_atomic (from); - vto =kmap_atomic (to); + vfrom =kmap_local_page (from); + vto =kmap_local_page (to);copy_page (vto, vfrom); -kunmap_atomic (vto); -kunmap_atomic (vfrom); +kunmap_local (vto); +kunmap_local (vfrom); }#endif
Signature · 1 line
2.28.0.rc0.12.gb6a658bd00c9
kernel test robot
build botRe: [PATCH V2 1/2] mm/highmem: Remove deprecated kmap_atomic
I love your patch! Yet something to improve:
Hi,
I love your patch! Yet something to improve:
[auto build test ERROR on hch-configfs/for-next]
[also build test ERROR on linus/master hnaz-linux-mm/master v5.10-rc7] [cannot apply to next-20201207]
[If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/ira-weiny-intel-com/Lift-memcpy_-to-from-_page-to-core/20201208-070017 base: git://git.infradead.org/users/hch/configfs.git for-next config: riscv-nommu_k210_defconfig (attached as .config) compiler: riscv64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/5b7d78e2f4cba24149752129e0397d102c501433
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review ira-weiny-intel-com/Lift-memcpy_-to-from-_page-to-core/20201208-070017 git checkout 5b7d78e2f4cba24149752129e0397d102c501433
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
All error/warnings (new ones prefixed by >>):
In file included from drivers/char/mem.c:24:
include/linux/highmem.h: In function 'clear_user_highpage':
>> include/linux/highmem.h:229:15: error: implicit declaration of function 'kmap_local_page'; did you mean 'kmap_to_page'? [-Werror=implicit-function-declaration]
229 | void *addr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
| kmap_to_page
>> include/linux/highmem.h:229:15: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
>> include/linux/highmem.h:231:2: error: implicit declaration of function 'kunmap_local' [-Werror=implicit-function-declaration]
231 | kunmap_local(addr);
| ^~~~~~~~~~~~
include/linux/highmem.h: In function 'clear_highpage':
include/linux/highmem.h:282:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
282 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'zero_user_segments':
include/linux/highmem.h:291:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
291 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'copy_user_highpage':
>> include/linux/highmem.h:324:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
324 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:325:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
325 | vto = kmap_local_page(to);
| ^
include/linux/highmem.h: In function 'copy_highpage':
include/linux/highmem.h:339:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
339 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:340:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
340 | vto = kmap_local_page(to);
| ^
cc1: some warnings being treated as errors
--
In file included from include/linux/pagemap.h:11,
from include/linux/blkdev.h:14,
from include/linux/blk-cgroup.h:23,
from include/linux/writeback.h:14,
from include/trace/events/random.h:8,
from drivers/char/random.c:348:
include/linux/highmem.h: In function 'clear_user_highpage':
>> include/linux/highmem.h:229:15: error: implicit declaration of function 'kmap_local_page'; did you mean 'kmap_to_page'? [-Werror=implicit-function-declaration]
229 | void *addr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
| kmap_to_page
>> include/linux/highmem.h:229:15: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
>> include/linux/highmem.h:231:2: error: implicit declaration of function 'kunmap_local' [-Werror=implicit-function-declaration]
231 | kunmap_local(addr);
| ^~~~~~~~~~~~
include/linux/highmem.h: In function 'clear_highpage':
include/linux/highmem.h:282:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
282 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'zero_user_segments':
include/linux/highmem.h:291:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
291 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'copy_user_highpage':
>> include/linux/highmem.h:324:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
324 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:325:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
325 | vto = kmap_local_page(to);
| ^
include/linux/highmem.h: In function 'copy_highpage':
include/linux/highmem.h:339:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
339 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:340:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
340 | vto = kmap_local_page(to);
| ^ drivers/char/random.c: At top level:
drivers/char/random.c:2296:6: warning: no previous prototype for 'add_hwgenerator_randomness' [-Wmissing-prototypes]
2296 | void add_hwgenerator_randomness(const char *buffer, size_t count,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +229 include/linux/highmem.h
223
224
225 /* when CONFIG_HIGHMEM is not set these will be plain clear/copy_page */
226 #ifndef clear_user_highpage
227 static inline void clear_user_highpage(struct page *page, unsigned long vaddr)
228 {
> 229 void *addr = kmap_local_page(page);
230 clear_user_page(addr, vaddr, page);
> 231 kunmap_local(addr);
232 }
233 #endif
234
235 #ifndef __HAVE_ARCH_ALLOC_ZEROED_USER_HIGHPAGE
236 /**
237 * __alloc_zeroed_user_highpage - Allocate a zeroed HIGHMEM page for a VMA with caller-specified movable GFP flags
238 * @movableflags: The GFP flags related to the pages future ability to move like __GFP_MOVABLE
239 * @vma: The VMA the page is to be allocated for
240 * @vaddr: The virtual address the page will be inserted into
241 *
242 * This function will allocate a page for a VMA but the caller is expected
243 * to specify via movableflags whether the page will be movable in the
244 * future or not
245 *
246 * An architecture may override this function by defining
247 * __HAVE_ARCH_ALLOC_ZEROED_USER_HIGHPAGE and providing their own
248 * implementation.
249 */
250 static inline struct page *
251 __alloc_zeroed_user_highpage(gfp_t movableflags,
252 struct vm_area_struct *vma,
253 unsigned long vaddr)
254 {
255 struct page *page = alloc_page_vma(GFP_HIGHUSER | movableflags,
256 vma, vaddr);
257
258 if (page)
259 clear_user_highpage(page, vaddr);
260
261 return page;
262 }
263 #endif
264
265 /**
266 * alloc_zeroed_user_highpage_movable - Allocate a zeroed HIGHMEM page for a VMA that the caller knows can move
267 * @vma: The VMA the page is to be allocated for
268 * @vaddr: The virtual address the page will be inserted into
269 *
270 * This function will allocate a page for a VMA that the caller knows will
271 * be able to migrate in the future using move_pages() or reclaimed
272 */
273 static inline struct page *
274 alloc_zeroed_user_highpage_movable(struct vm_area_struct *vma,
275 unsigned long vaddr)
276 {
277 return __alloc_zeroed_user_highpage(__GFP_MOVABLE, vma, vaddr);
278 }
279
280 static inline void clear_highpage(struct page *page)
281 {
> 282 void *kaddr = kmap_local_page(page);
283 clear_page(kaddr);
284 kunmap_local(kaddr);
285 }
286
287 static inline void zero_user_segments(struct page *page,
288 unsigned start1, unsigned end1,
289 unsigned start2, unsigned end2)
290 {
291 void *kaddr = kmap_local_page(page);
292
293 BUG_ON(end1 > PAGE_SIZE || end2 > PAGE_SIZE);
294
295 if (end1 > start1)
296 memset(kaddr + start1, 0, end1 - start1);
297
298 if (end2 > start2)
299 memset(kaddr + start2, 0, end2 - start2);
300
301 kunmap_local(kaddr);
302 flush_dcache_page(page);
303 }
304
305 static inline void zero_user_segment(struct page *page,
306 unsigned start, unsigned end)
307 {
308 zero_user_segments(page, start, end, 0, 0);
309 }
310
311 static inline void zero_user(struct page *page,
312 unsigned start, unsigned size)
313 {
314 zero_user_segments(page, start, start + size, 0, 0);
315 }
316
317 #ifndef __HAVE_ARCH_COPY_USER_HIGHPAGE
318
319 static inline void copy_user_highpage(struct page *to, struct page *from,
320 unsigned long vaddr, struct vm_area_struct *vma)
321 {
322 char *vfrom, *vto;
323
> 324 vfrom = kmap_local_page(from); 325 vto = kmap_local_page(to);
326 copy_user_page(vto, vfrom, vaddr, to);
327 kunmap_local(vto);
328 kunmap_local(vfrom);
329 }
330
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
PATCH v2 2/2 mm/highmem: Lift memcpy_[to|from]_page to core
In reply to [email protected]From: Ira Weiny <[email protected]>
Working through a conversion to a call such as kmap_thread() revealed many places where the pattern kmap/memcpy/kunmap occurred.
Eric Biggers, Matthew Wilcox, Christoph Hellwig, Dan Williams, and Al Viro all suggested putting this code into helper functions. Al Viro further pointed out that these functions already existed in the iov_iter code.[1]
Placing these functions in 'highmem.h' is suboptimal especially with the changes being proposed in the functionality of kmap. From a caller perspective including/using 'highmem.h' implies that the functions defined in that header are only required when highmem is in use which is increasingly not the case with modern processors. Some headers like mm.h or string.h seem ok but don't really portray the functionality well. 'pagemap.h', on the other hand, makes sense and is already included in many of the places we want to convert.
Another alternative would be to create a new header for the promoted memcpy functions, but it masks the fact that these are designed to copy to/from pages using the kernel direct mappings and complicates matters with a new header.
Lift memcpy_to_page() and memcpy_from_page() to pagemap.h.
Remove memzero_page() in favor of zero_user() to zero a page.
Add a memcpy_page(), memmove_page, and memset_page() to cover more kmap/mem*/kunmap. patterns.
Finally use kmap_local_page() in all the new calls.
[1] https://lore.kernel.org/lkml/[email protected]/
https://lore.kernel.org/lkml/[email protected]/
---
Changes for V2:
From Thomas Gleixner
Change kmap_atomic() to kmap_local_page() after basing on tip/core/mm
From Joonas Lahtinen
Reverse offset/val in memset_page()
--- include/linux/pagemap.h | 44 +++++++++++++++++++++++++++++++++++++++++ lib/iov_iter.c | 26 +++--------------------- 2 files changed, 47 insertions(+), 23 deletions(-)
include/linux/pagemap.h +44 -0
@@ -1028,4 +1028,48 @@ unsigned int i_blocks_per_page(struct inode *inode, struct page *page) {return thp_size (page) >> inode->i_blkbits; } + +static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page); +memcpy (dst + dst_off, src + src_off, len); +kunmap_local (src); +kunmap_local (dst); +} + +static inline void memmove_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page); +memmove (dst + dst_off, src + src_off, len); +kunmap_local (src); +kunmap_local (dst); +} + +static inline void memcpy_from_page (char *to,struct page *page,size_t offset,size_t len) +{ +char *from =kmap_local_page (page); +memcpy (to, from + offset, len); +kunmap_local (from); +} + +static inline void memcpy_to_page (struct page *page,size_t offset,const char *from,size_t len) +{ +char *to =kmap_local_page (page); +memcpy (to + offset, from, len); +kunmap_local (to); +} + +static inline void memset_page (struct page *page,size_t offset,int val,size_t len) +{ +char *addr =kmap_local_page (page); +memset (addr + offset, val, len); +kunmap_local (addr); +} +#endif /* _LINUX_PAGEMAP_H */
lib/iov_iter.c +3 -23
@@ -5,6 +5,7 @@#include <linux/fault-inject-usercopy.h> #include <linux/uio.h> #include <linux/pagemap.h> +#include <linux/highmem.h> #include <linux/slab.h> #include <linux/vmalloc.h> #include <linux/splice.h>
@@ -466,27 +467,6 @@ void iov_iter_init(struct iov_iter *i, unsigned int direction, }EXPORT_SYMBOL (iov_iter_init); -static void memcpy_from_page (char *to,struct page *page,size_t offset,size_t len) -{ -char *from =kmap_atomic (page); -memcpy (to, from + offset, len); -kunmap_atomic (from); -} - -static void memcpy_to_page (struct page *page,size_t offset,const char *from,size_t len) -{ -char *to =kmap_atomic (page); -memcpy (to + offset, from, len); -kunmap_atomic (to); -} - -static void memzero_page (struct page *page,size_t offset,size_t len) -{ -char *addr =kmap_atomic (page); -memset (addr + offset,0 , len); -kunmap_atomic (addr); -} -static inline bool allocated (struct pipe_buffer *buf) {return buf->ops == &default_pipe_buf_ops;
@@ -964,7 +944,7 @@ static size_t pipe_zero(size_t bytes, struct iov_iter *i) do { size_t chunk = min_t(size_t, n, PAGE_SIZE - off); - memzero_page(pipe->bufs[i_head & p_mask].page, off, chunk); + zero_user(pipe->bufs[i_head & p_mask].page, off, chunk); i->head = i_head; i->iov_offset = off + chunk; n -= chunk;
@@ -981,7 +961,7 @@ size_t iov_iter_zero(size_t bytes, struct iov_iter *i)return pipe_zero (bytes, i);iterate_and_advance (i, bytes, v,clear_user (v.iov_base, v.iov_len), -memzero_page (v.bv_page, v.bv_offset, v.bv_len), +zero_user (v.bv_page, v.bv_offset, v.bv_len),memset (v.iov_base,0 , v.iov_len) )
Signature · 1 line
2.28.0.rc0.12.gb6a658bd00c9
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1037
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
include/linux/pagemap.h +6
-0+static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);
I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1048
Quoted 11 lines
include/linux/pagemap.h +11
-0+memcpy (dst + dst_off, src + src_off, len); +kunmap_local (src); +kunmap_local (dst); +} + +static inline void memmove_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1056
Quoted 8 lines
include/linux/pagemap.h +8
-0+memmove (dst + dst_off, src + src_off, len); +kunmap_local (src); +kunmap_local (dst); +} + +static inline void memcpy_from_page (char *to,struct page *page,size_t offset,size_t len) +{ +char *from =kmap_local_page (page);
BUG_ON(offset + len > PAGE_SIZE);
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1063
Quoted 7 lines
include/linux/pagemap.h +7
-0+memcpy (to, from + offset, len); +kunmap_local (from); +} + +static inline void memcpy_to_page (struct page *page,size_t offset,const char *from,size_t len) +{ +char *to =kmap_local_page (page);
BUG_ON(offset + len > PAGE_SIZE);
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1070
Quoted 7 lines
include/linux/pagemap.h +7
-0+memcpy (to + offset, from, len); +kunmap_local (to); +} + +static inline void memset_page (struct page *page,size_t offset,int val,size_t len) +{ +char *addr =kmap_local_page (page);
BUG_ON(offset + len > PAGE_SIZE);
Quoted 5 lines
include/linux/pagemap.h +4
-0+memset (addr + offset, val, len); + kunmap_local(addr); +} +#endif /* _LINUX_PAGEMAP_H */
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 11 lines · Matthew Wilcox
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1037
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
include/linux/pagemap.h +6
-0+static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);I appreciate you've only moved these, but please add:
Quoted 1 line
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);
I imagine it's not outside the realm of possibility that some driver on CONFIG_HIGHMEM=n is violating this assumption and getting away with it because kmap_atomic() of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 12 lines · Dan Williams
Quoted 11 lines · Matthew Wilcox
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1037
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
include/linux/pagemap.h +6
-0+static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);I appreciate you've only moved these, but please add:
Quoted 7 lines
Quoted 1 line
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?
As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory? I suppose ideally ...
if (WARN_ON(dst_off + len > PAGE_SIZE)) len = PAGE_SIZE - dst_off; if (WARN_ON(src_off + len > PAGE_SIZE)) len = PAGE_SIZE - src_off;
and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1037
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
include/linux/pagemap.h +6
-0+static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);
Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 39 lines · Dan Williams
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1037
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
include/linux/pagemap.h +6
-0+static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Quoted 7 lines
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
So I decided to just sleep on this because I was recently told to not introduce new WARN_ON's[1]
I don't think that truncating len is worth the effort. The conversions being done should all 'work' At least corrupting users data in the same way as it used to... ;-) I'm ok with adding the WARN_ON's and I have modified the patch to do so while I work through the 0-day issues. (not sure what is going on there.)
However, are we ok with adding the WARN_ON's given what Greg KH told me? This is a bit more critical than the PKS API in that it could result in corrupt data.
Ira
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 57 lines · Ira Weiny
Quoted 39 lines · Dan Williams
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1037
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
include/linux/pagemap.h +6
-0+static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Quoted 7 lines
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
So I decided to just sleep on this because I was recently told to not introduce new WARN_ON's[1]
I don't think that truncating len is worth the effort. The conversions being done should all 'work' At least corrupting users data in the same way as it used to... ;-) I'm ok with adding the WARN_ON's and I have modified the patch to do so while I work through the 0-day issues. (not sure what is going on there.)
Quoted 3 lines
However, are we ok with adding the WARN_ON's given what Greg KH told me? This is a bit more critical than the PKS API in that it could result in corrupt data.
zero_user_segments contains:
BUG_ON(end1 > page_size(page) || end2 > page_size(page));
These should be consistent. I think we've demonstrated that there is no good option here.
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 63 lines · Matthew Wilcox
Quoted 57 lines · Ira Weiny
Quoted 39 lines · Dan Williams
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
Review
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
(quoted diff) +6
-0+static inline void memcpy_page(struct page *dst_page, size_t dst_off, + struct page *src_page, size_t src_off, + size_t len) +{ + char *dst = kmap_local_page(dst_page); + char *src = kmap_local_page(src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Quoted 7 lines
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
So I decided to just sleep on this because I was recently told to not introduce new WARN_ON's[1]
I don't think that truncating len is worth the effort. The conversions being done should all 'work' At least corrupting users data in the same way as it used to... ;-) I'm ok with adding the WARN_ON's and I have modified the patch to do so while I work through the 0-day issues. (not sure what is going on there.)
Quoted 3 lines
However, are we ok with adding the WARN_ON's given what Greg KH told me? This is a bit more critical than the PKS API in that it could result in corrupt data.
Quoted 6 lines
zero_user_segmentscontains:BUG_ON(end1 > page_size(page) || end2 > page_size(page));These should be consistent. I think we've demonstrated that there is no good option here.
True, but these helpers are being deployed to many new locations where they were not used before.
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 66 lines · Dan Williams
Quoted 65 lines · Matthew Wilcox
Quoted 57 lines · Ira Weiny
Quoted 39 lines · Dan Williams
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
Review
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
(quoted diff) +6
-0+static inline void memcpy_page(struct page *dst_page, size_t dst_off, + struct page *src_page, size_t src_off, + size_t len) +{ + char *dst = kmap_local_page(dst_page); + char *src = kmap_local_page(src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Quoted 7 lines
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
So I decided to just sleep on this because I was recently told to not introduce new WARN_ON's[1]
I don't think that truncating len is worth the effort. The conversions being done should all 'work' At least corrupting users data in the same way as it used to... ;-) I'm ok with adding the WARN_ON's and I have modified the patch to do so while I work through the 0-day issues. (not sure what is going on there.)
Quoted 3 lines
However, are we ok with adding the WARN_ON's given what Greg KH told me? This is a bit more critical than the PKS API in that it could result in corrupt data.
zero_user_segmentscontains:
Quoted 7 lines
Quoted 4 lines
BUG_ON(end1 > page_size(page) || end2 > page_size(page));These should be consistent. I think we've demonstrated that there is no good option here.
True, but these helpers are being deployed to many new locations where they were not used before.
So what's your preferred poison?
1. Corrupt random data in whatever's been mapped into the next page (which is what the helpers currently do)
2. Copy less data than requested
3. Crash
4. Something else
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 72 lines · Matthew Wilcox
Quoted 71 lines · Dan Williams
Quoted 69 lines · Matthew Wilcox
Quoted 57 lines · Ira Weiny
Quoted 39 lines · Dan Williams
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
Review
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
(quoted diff) +6
-0+static inline void memcpy_page(struct page *dst_page, size_t dst_off, + struct page *src_page, size_t src_off, + size_t len) +{ + char *dst = kmap_local_page(dst_page); + char *src = kmap_local_page(src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Quoted 7 lines
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
So I decided to just sleep on this because I was recently told to not introduce new WARN_ON's[1]
I don't think that truncating len is worth the effort. The conversions being done should all 'work' At least corrupting users data in the same way as it used to... ;-) I'm ok with adding the WARN_ON's and I have modified the patch to do so while I work through the 0-day issues. (not sure what is going on there.)
Quoted 3 lines
However, are we ok with adding the WARN_ON's given what Greg KH told me? This is a bit more critical than the PKS API in that it could result in corrupt data.
zero_user_segmentscontains:BUG_ON(end1 > page_size(page) || end2 > page_size(page));These should be consistent. I think we've demonstrated that there is no good option here.
Quoted 7 lines
Quoted 2 lines
True, but these helpers are being deployed to many new locations where they were not used before.
So what's your preferred poison?
1. Corrupt random data in whatever's been mapped into the next page (which is what the helpers currently do)
Please no.
Quoted 1 line
2. Copy less data than requested
This sounds like the germination event for a research paper showing that 63% of callers never notice. ;)
Quoted 1 line
3. Crash
Useful as a debug tool?
Quoted 1 line
4. Something else
Return bytes copied like we do for writes that didn't quite work?
--D
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 88 lines · Darrick J. Wong
Quoted 72 lines · Matthew Wilcox
Quoted 71 lines · Dan Williams
Quoted 69 lines · Matthew Wilcox
Quoted 57 lines · Ira Weiny
Quoted 39 lines · Dan Williams
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
Review
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
(quoted diff) +6
-0+static inline void memcpy_page(struct page *dst_page, size_t dst_off, + struct page *src_page, size_t src_off, + size_t len) +{ + char *dst = kmap_local_page(dst_page); + char *src = kmap_local_page(src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Quoted 7 lines
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
So I decided to just sleep on this because I was recently told to not introduce new WARN_ON's[1]
I don't think that truncating len is worth the effort. The conversions being done should all 'work' At least corrupting users data in the same way as it used to... ;-) I'm ok with adding the WARN_ON's and I have modified the patch to do so while I work through the 0-day issues. (not sure what is going on there.)
Quoted 3 lines
However, are we ok with adding the WARN_ON's given what Greg KH told me? This is a bit more critical than the PKS API in that it could result in corrupt data.
zero_user_segmentscontains:BUG_ON(end1 > page_size(page) || end2 > page_size(page));These should be consistent. I think we've demonstrated that there is no good option here.
Quoted 7 lines
Quoted 2 lines
True, but these helpers are being deployed to many new locations where they were not used before.
So what's your preferred poison?
1. Corrupt random data in whatever's been mapped into the next page (which is what the helpers currently do)
Please no.
Quoted 1 line
2. Copy less data than requested
This sounds like the germination event for a research paper showing that 63% of callers never notice. ;)
Quoted 7 lines
Quoted 1 line
3. Crash
Useful as a debug tool?
Quoted 1 line
4. Something else
Return bytes copied like we do for writes that didn't quite work?
... to learn that 87% of callers never check the return value, 10% of them do the wrong thing and the remainder have never been tested?
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
In reply to Darrick J. WongOn Tue, Dec 8, 2020 at 2:49 PM Darrick J. Wong <[email protected]> wrote:
[..]
Quoted 6 lines
Quoted 4 lines
So what's your preferred poison?
1. Corrupt random data in whatever's been mapped into the next page (which is what the helpers currently do)
Please no.
My assertion is that the kernel can't know it's corruption, it can only know that the driver is abusing the API. So over-copy and WARN seems better than violently regress by crashing what might have been working silently before.
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 7 lines · Dan Williams
On Tue, Dec 8, 2020 at 2:49 PM Darrick J. Wong <[email protected]> wrote:
[..]Quoted 5 lines
Quoted 4 lines
So what's your preferred poison?
1. Corrupt random data in whatever's been mapped into the next page (which is what the helpers currently do)
Quoted 6 lines
Quoted 1 line
Please no.
My assertion is that the kernel can't know it's corruption, it can only know that the driver is abusing the API. So over-copy and WARN seems better than violently regress by crashing what might have been working silently before.
Right now we have a mixed bag. zero_user() [and it's variants, circa 2008] does a BUG_ON.[0] While the other ones do nothing; clear_highpage(), clear_user_highpage(), copy_user_highpage(), and copy_highpage().
While continuing to audit the code I don't see any users who would violating the API with a simple conversion of the code. The calls which I have worked on [which is many at this point] all have checks in place which are well aware of page boundaries.
Therefore, I tend to agree with Dan that if anything is to be done it should be a WARN_ON() which is only going to throw an error that something has probably been wrong all along and should be fixed but continue running as before.
BUG_ON() is a very big hammer. And I don't think that Linus is going to appreciate a BUG_ON here.[1] Callers of this API should be well aware that they are operating on a page and that specifying parameters beyond the bounds of a page are going to have bad consequences...
Furthermore, I'm still leery of adding the WARN_ON's because Greg KH says many people will be converting them to BUG_ON's via panic-on-warn anyway. But at least that is their choice.
FWIW I think this is a 'bad BUG_ON' use because we are "checking something that we know we might be getting wrong".[1] And because, "BUG() is only good for something that never happens and that we really have no other option for".[2]
IMO, These calls are like memcpy/memmove. memcpy/memmove don't validate bounds and developers have lived with those constructs for a long time.
Ira
[0] BTW, After writing this email, with various URL research, I think this BUG_ON() is also probably wrong...
[1]
<quote> ... It's [BUG_ON] not a "let's check that everybody did things right", it's a "this is a major design rule in this core code". ... </quote> -- Linus (https://lkml.org/lkml/2016/10/4/337)
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 3 lines · Ira Weiny
Right now we have a mixed bag.
zero_user()[and it's variants, circa 2008] does a BUG_ON.[0] While the other ones do nothing;clear_highpage(),clear_user_highpage(),copy_user_highpage(), andcopy_highpage().
Erm, those functions operate on the entire PAGE_SIZE. There's nothing for them to check.
Quoted 4 lines
While continuing to audit the code I don't see any users who would violating the API with a simple conversion of the code. The calls which I have worked on [which is many at this point] all have checks in place which are well aware of page boundaries.
Oh good, then this BUG_ON won't trigger.
Quoted 3 lines
Therefore, I tend to agree with Dan that if anything is to be done it should be a
WARN_ON()which is only going to throw an error that something has probably been wrong all along and should be fixed but continue running as before.
Silent data corruption is for ever. Are you absolutely sure nobody has done:
page = alloc_pages(GFP_HIGHUSER_MOVABLE, 3); memcpy_to_page(page, PAGE_SIZE * 2, p, PAGE_SIZE * 2);
because that will work fine if the pages come from ZONE_NORMAL and fail miserably if they came from ZONE_HIGHMEM.
Quoted 3 lines
FWIW I think this is a 'bad
BUG_ON' use because we are "checking something that we know we might be getting wrong".[1] And because, "BUG()is only good for something that never happens and that we really have no other option for".[2]
BUG() is our only option here. Both limiting how much we copy or copying the requested amount result in data corruption or leaking information to a process that isn't supposed to see it.
What Linus is railing against is the developers who say "Oh, I don't know what to do here, I'll just BUG()". That's not the case here. We've thought about it. We've discussed it. There's NO GOOD OPTION.
Unless you want to do the moral equivalent of this:
I think that would look something like this ...
void memcpy_to_page(struct page *page, size_t offset, const char *from,
size_t len)
{
page += offset / PAGE_SIZE;
offset %= PAGE_SIZE;
while (len) {
char *to = kmap_atomic(page);
size_t bytes = min(len, PAGE_SIZE - offset);
memcpy(to + offset, from, len);
kunmap_atomic(to);
len -= bytes;
offset = 0;
page++;
}
}Now 32-bit highmem will do the same thing as 64-bit for my example above, just more slowly. Untested, obviously.
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 20 lines · Matthew Wilcox
Quoted 3 lines · Ira Weiny
Right now we have a mixed bag.
zero_user()[and it's variants, circa 2008] does a BUG_ON.[0] While the other ones do nothing;clear_highpage(),clear_user_highpage(),copy_user_highpage(), andcopy_highpage().Erm, those functions operate on the entire
PAGE_SIZE. There's nothing for them to check.Quoted 4 lines
While continuing to audit the code I don't see any users who would violating the API with a simple conversion of the code. The calls which I have worked on [which is many at this point] all have checks in place which are well aware of page boundaries.
Oh good, then this
BUG_ONwon't trigger.Quoted 3 lines
Therefore, I tend to agree with Dan that if anything is to be done it should be a
WARN_ON()which is only going to throw an error that something has probably been wrong all along and should be fixed but continue running as before.
Quoted 8 lines
Silent data corruption is for ever. Are you absolutely sure nobody has done:
page = alloc_pages(GFP_HIGHUSER_MOVABLE, 3); memcpy_to_page(page, PAGE_SIZE * 2, p, PAGE_SIZE * 2);because that will work fine if the pages come from
ZONE_NORMALand fail miserably if they came fromZONE_HIGHMEM.
...and violently regress with the BUG_ON.
The question to me is: which is more likely that any bad usages have been covered up by being limited to ZONE_NORMAL / 64-bit only, or that silent data corruption has been occurring with no ill effects?
Quoted 7 lines
Quoted 3 lines
FWIW I think this is a 'bad
BUG_ON' use because we are "checking something that we know we might be getting wrong".[1] And because, "BUG()is only good for something that never happens and that we really have no other option for".[2]
BUG()is our only option here. Both limiting how much we copy or copying the requested amount result in data corruption or leaking information to a process that isn't supposed to see it.
At a minimum I think this should be debated in a follow on patch to add assertion checking where there was none before. There is no evidence of a page being overrun in the audit Ira performed.
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 9 lines · Dan Williams
Quoted 8 lines · Matthew Wilcox
Quoted 3 lines · Ira Weiny
Therefore, I tend to agree with Dan that if anything is to be done it should be a
WARN_ON()which is only going to throw an error that something has probably been wrong all along and should be fixed but continue running as before.Silent data corruption is for ever. Are you absolutely sure nobody has done:
Quoted 7 lines
Quoted 5 lines
page = alloc_pages(GFP_HIGHUSER_MOVABLE, 3); memcpy_to_page(page, PAGE_SIZE * 2, p, PAGE_SIZE * 2);because that will work fine if the pages come from
ZONE_NORMALand fail miserably if they came fromZONE_HIGHMEM....and violently regress with the
BUG_ON.
... which is what we want, no?
Quoted 3 lines
The question to me is: which is more likely that any bad usages have been covered up by being limited to
ZONE_NORMAL/ 64-bit only, or that silent data corruption has been occurring with no ill effects?
I wouldn't be at all surprised to learn that there is silent data corruption on 32-bit systems with HIGHMEM. Would you? How much testing do you do on 32-bit HIGHMEM systems?
Actually, I wouldn't be at all surprised if we can hit this problem today. Look at this:
size_t _copy_from_iter(void *addr, size_t bytes, struct iov_iter *i)
{
char *to = addr;
if (unlikely(iov_iter_is_pipe(i))) {
WARN_ON(1);
return 0;
}
if (iter_is_iovec(i))
might_fault();
iterate_and_advance(i, bytes, v,
copyin((to += v.iov_len) - v.iov_len, v.iov_base, v.iov_len),
memcpy_from_page((to += v.bv_len) - v.bv_len, v.bv_page,
v.bv_offset, v.bv_len),
memcpy((to += v.iov_len) - v.iov_len, v.iov_base, v.iov_len)
)
return bytes;
}EXPORT_SYMBOL(_copy_from_iter);
There's a lot of macrology in there, so for those following along who aren't familiar with the iov_iter code, if the iter is operating on a bvec, then iterate_and_advance() will call memcpy_from_page(), passing it the bv_page, bv_offset and bv_len stored in the bvec. Since 2019, Linux has supported multipage bvecs (commit 07173c3ec276). So bv_len absolutely *can* be > PAGE_SIZE.
Does this ever happen in practice? I have no idea; I don't know whether any multipage BIOs are currently handed to copy_from_iter(). But I have no confidence in your audit if you didn't catch this one.
Quoted 11 lines
Quoted 7 lines
Quoted 3 lines
FWIW I think this is a 'bad
BUG_ON' use because we are "checking something that we know we might be getting wrong".[1] And because, "BUG()is only good for something that never happens and that we really have no other option for".[2]
BUG()is our only option here. Both limiting how much we copy or copying the requested amount result in data corruption or leaking information to a process that isn't supposed to see it.At a minimum I think this should be debated in a follow on patch to add assertion checking where there was none before. There is no evidence of a page being overrun in the audit Ira performed.
If we put in into a separate patch, someone will suggest backing out the patch which tells us that there's a problem. You know, like this guy ...
https://lore.kernel.org/linux-mm/CAPcyv4jNVroYmirzKw_=CsEixOEACdL3M1Wc4xjd_TFv3h+o8Q@mail.gmail.com/
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
On Wed, Dec 9, 2020 at 12:14 PM Matthew Wilcox <[email protected]> wrote:
[..]
Quoted 3 lines
If we put in into a separate patch, someone will suggest backing out the patch which tells us that there's a problem. You know, like this guy ...
https://lore.kernel.org/linux-mm/CAPcyv4jNVroYmirzKw_=CsEixOEACdL3M1Wc4xjd_TFv3h+o8Q@mail.gmail.com/
...and that person, like in this case, will be told 'no' and go on to find / fix the real problem.
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
In reply to Matthew WilcoxQuoted 58 lines · Matthew Wilcox
Quoted 9 lines · Dan Williams
Quoted 8 lines · Matthew Wilcox
Quoted 3 lines · Ira Weiny
Therefore, I tend to agree with Dan that if anything is to be done it should be a
WARN_ON()which is only going to throw an error that something has probably been wrong all along and should be fixed but continue running as before.Silent data corruption is for ever. Are you absolutely sure nobody has done:
Quoted 7 lines
Quoted 5 lines
page = alloc_pages(GFP_HIGHUSER_MOVABLE, 3); memcpy_to_page(page, PAGE_SIZE * 2, p, PAGE_SIZE * 2);because that will work fine if the pages come from
ZONE_NORMALand fail miserably if they came fromZONE_HIGHMEM....and violently regress with the
BUG_ON.... which is what we want, no?
Quoted 3 lines
The question to me is: which is more likely that any bad usages have been covered up by being limited to
ZONE_NORMAL/ 64-bit only, or that silent data corruption has been occurring with no ill effects?I wouldn't be at all surprised to learn that there is silent data corruption on 32-bit systems with HIGHMEM. Would you? How much testing do you do on 32-bit HIGHMEM systems?
Actually, I wouldn't be at all surprised if we can hit this problem today. Look at this:
size_t_copy_from_iter(void *addr, size_t bytes, struct iov_iter *i){ char *to = addr; if (unlikely(iov_iter_is_pipe(i))) { WARN_ON(1); return 0; } if (iter_is_iovec(i)) might_fault(); iterate_and_advance(i, bytes, v, copyin((to += v.iov_len) - v.iov_len, v.iov_base, v.iov_len), memcpy_from_page((to += v.bv_len) - v.bv_len, v.bv_page, v.bv_offset, v.bv_len), memcpy((to += v.iov_len) - v.iov_len, v.iov_base, v.iov_len) ) return bytes; }
EXPORT_SYMBOL(_copy_from_iter);There's a lot of macrology in there, so for those following along who aren't familiar with the
iov_itercode, if the iter is operating on a bvec, theniterate_and_advance()will callmemcpy_from_page(), passing it thebv_page,bv_offsetandbv_lenstored in the bvec. Since 2019, Linux has supported multipage bvecs (commit07173c3ec276). Sobv_lenabsolutely *can* be >PAGE_SIZE.
Quoted 3 lines
Does this ever happen in practice? I have no idea; I don't know whether any multipage BIOs are currently handed to
copy_from_iter(). But I have no confidence in your audit if you didn't catch this one.
Ah... This call site has been there since 2014 and is not a new caller I have been 'auditing'.[1]
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
Quoted 4 lines
FWIW I think this is a 'bad
BUG_ON' use because we are "checking something that we know we might be getting wrong".[1] And because, "BUG()is only good for something that never happens and that we really have no other option for".[2]
BUG()is our only option here. Both limiting how much we copy or copying the requested amount result in data corruption or leaking information to a process that isn't supposed to see it.
Quoted 7 lines
Quoted 3 lines
At a minimum I think this should be debated in a follow on patch to add assertion checking where there was none before. There is no evidence of a page being overrun in the audit Ira performed.
If we put in into a separate patch, someone will suggest backing out the patch which tells us that there's a problem. You know, like this guy ...
https://lore.kernel.org/linux-mm/CAPcyv4jNVroYmirzKw_=CsEixOEACdL3M1Wc4xjd_TFv3h+o8Q@mail.gmail.com/
I'm not following this. Regardless I've already added the BUG_ON's.
Ira
[1]
commit 0dbca9a4b5d69a7e4b8c1d55b98312fcd9aafcf7
Author: Al Viro <[email protected]> Date: Thu Nov 27 14:26:43 2014 -0500
iov_iter.c: convert copy_from_iter() to iterate_and_advance
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
In reply to Ira WeinyQuoted 58 lines · Ira Weiny
Quoted 39 lines · Dan Williams
Quoted 16 lines · Matthew Wilcox
Quoted 14 lines · Dan Williams
Quoted 12 lines · Matthew Wilcox
include/linux/pagemap.h unsigned int i_blocks_per_page(struct inode *inode, struct page *page) · line 1037
Quoted 6 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
include/linux/pagemap.h +6
-0+static inline void memcpy_page (struct page *dst_page,size_t dst_off, +struct page *src_page,size_t src_off, +size_t len) +{ +char *dst =kmap_local_page (dst_page); +char *src =kmap_local_page (src_page);I appreciate you've only moved these, but please add:
BUG_ON(dst_off + len > PAGE_SIZE || src_off + len > PAGE_SIZE);Quoted 8 lines
Quoted 5 lines
I imagine it's not outside the realm of possibility that some driver on
CONFIG_HIGHMEM=nis violating this assumption and getting away with it becausekmap_atomic()of contiguous pages "just works (TM)". Shouldn't this WARN rather than BUG so that the user can report the buggy driver and not have a dead system?As opposed to (on a HIGHMEM=y system) silently corrupting data that is on the next page of memory?
Wouldn't it fault in HIGHMEM=y case? I guess not necessarily...
Quoted 10 lines
I suppose ideally ...
if (
WARN_ON(dst_off + len > PAGE_SIZE))
len =PAGE_SIZE-dst_off;
if (WARN_ON(src_off + len > PAGE_SIZE))
len =PAGE_SIZE-src_off;and then we just truncate the data of the offending caller instead of corrupting innocent data that happens to be adjacent. Although that's not ideal either ... I dunno, what's the least bad poison to drink here?
Quoted 7 lines
Right, if the driver was relying on "corruption" for correct operation.
If corruption actual were happening in practice wouldn't there have been screams by now? Again, not necessarily...
At least with just plain WARN the kernel will start screaming on the user's behalf, and if it worked before it will keep working.
So I decided to just sleep on this because I was recently told to not introduce new WARN_ON's[1]
I don't think that truncating len is worth the effort. The conversions being done should all 'work' At least corrupting users data in the same way as it used to... ;-) I'm ok with adding the WARN_ON's and I have modified the patch to do so while I work through the 0-day issues. (not sure what is going on there.)
Quoted 3 lines
However, are we ok with adding the WARN_ON's given what Greg KH told me? This is a bit more critical than the PKS API in that it could result in corrupt data.
That situation was a bit different in my mind because the default fallback stub path has typically never had WARN_ON even if it's never supposed to be called.
kernel test robot
build botRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
In reply to [email protected]I love your patch! Perhaps something to improve:
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on hch-configfs/for-next]
[also build test WARNING on linus/master v5.10-rc7]
[cannot apply to hnaz-linux-mm/master next-20201207]
[If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/ira-weiny-intel-com/Lift-memcpy_-to-from-_page-to-core/20201208-070017 base: git://git.infradead.org/users/hch/configfs.git for-next config: riscv-nommu_k210_defconfig (attached as .config) compiler: riscv64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/23e6d3f08a315c6e70fde3d63a275c91e1dcb0ee
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review ira-weiny-intel-com/Lift-memcpy_-to-from-_page-to-core/20201208-070017 git checkout 23e6d3f08a315c6e70fde3d63a275c91e1dcb0ee
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
All warnings (new ones prefixed by >>):
In file included from drivers/char/mem.c:24:
include/linux/highmem.h: In function 'clear_user_highpage':
include/linux/highmem.h:229:15: error: implicit declaration of function 'kmap_local_page'; did you mean 'kmap_to_page'? [-Werror=implicit-function-declaration]
229 | void *addr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
| kmap_to_page
include/linux/highmem.h:229:15: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
include/linux/highmem.h:231:2: error: implicit declaration of function 'kunmap_local' [-Werror=implicit-function-declaration]
231 | kunmap_local(addr);
| ^~~~~~~~~~~~
include/linux/highmem.h: In function 'clear_highpage':
include/linux/highmem.h:282:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
282 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'zero_user_segments':
include/linux/highmem.h:291:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
291 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'copy_user_highpage':
include/linux/highmem.h:324:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
324 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:325:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
325 | vto = kmap_local_page(to);
| ^
include/linux/highmem.h: In function 'copy_highpage':
include/linux/highmem.h:339:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
339 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:340:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
340 | vto = kmap_local_page(to);
| ^
In file included from include/linux/blkdev.h:14,
from include/linux/backing-dev.h:15,
from drivers/char/mem.c:25:
include/linux/pagemap.h: In function 'memcpy_page':
>> include/linux/pagemap.h:1036:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1036 | char *dst = kmap_local_page(dst_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h:1037:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1037 | char *src = kmap_local_page(src_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memmove_page':
include/linux/pagemap.h:1047:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1047 | char *dst = kmap_local_page(dst_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h:1048:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1048 | char *src = kmap_local_page(src_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memcpy_from_page':
include/linux/pagemap.h:1056:15: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1056 | char *from = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memcpy_to_page':
include/linux/pagemap.h:1063:13: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1063 | char *to = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memset_page':
include/linux/pagemap.h:1070:15: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1070 | char *addr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
--
In file included from include/linux/pagemap.h:11,
from include/linux/blkdev.h:14,
from include/linux/blk-cgroup.h:23,
from include/linux/writeback.h:14,
from include/trace/events/random.h:8,
from drivers/char/random.c:348:
include/linux/highmem.h: In function 'clear_user_highpage':
include/linux/highmem.h:229:15: error: implicit declaration of function 'kmap_local_page'; did you mean 'kmap_to_page'? [-Werror=implicit-function-declaration]
229 | void *addr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
| kmap_to_page
include/linux/highmem.h:229:15: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
include/linux/highmem.h:231:2: error: implicit declaration of function 'kunmap_local' [-Werror=implicit-function-declaration]
231 | kunmap_local(addr);
| ^~~~~~~~~~~~
include/linux/highmem.h: In function 'clear_highpage':
include/linux/highmem.h:282:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
282 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'zero_user_segments':
include/linux/highmem.h:291:16: warning: initialization of 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
291 | void *kaddr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/highmem.h: In function 'copy_user_highpage':
include/linux/highmem.h:324:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
324 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:325:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
325 | vto = kmap_local_page(to);
| ^
include/linux/highmem.h: In function 'copy_highpage':
include/linux/highmem.h:339:8: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
339 | vfrom = kmap_local_page(from);
| ^
include/linux/highmem.h:340:6: warning: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
340 | vto = kmap_local_page(to);
| ^
In file included from include/linux/blkdev.h:14,
from include/linux/blk-cgroup.h:23,
from include/linux/writeback.h:14,
from include/trace/events/random.h:8,
from drivers/char/random.c:348:
include/linux/pagemap.h: In function 'memcpy_page':
>> include/linux/pagemap.h:1036:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1036 | char *dst = kmap_local_page(dst_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h:1037:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1037 | char *src = kmap_local_page(src_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memmove_page':
include/linux/pagemap.h:1047:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1047 | char *dst = kmap_local_page(dst_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h:1048:14: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1048 | char *src = kmap_local_page(src_page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memcpy_from_page':
include/linux/pagemap.h:1056:15: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1056 | char *from = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memcpy_to_page':
include/linux/pagemap.h:1063:13: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1063 | char *to = kmap_local_page(page);
| ^~~~~~~~~~~~~~~
include/linux/pagemap.h: In function 'memset_page':
include/linux/pagemap.h:1070:15: warning: initialization of 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
1070 | char *addr = kmap_local_page(page);
| ^~~~~~~~~~~~~~~ drivers/char/random.c: At top level:
drivers/char/random.c:2296:6: warning: no previous prototype for 'add_hwgenerator_randomness' [-Wmissing-prototypes]
2296 | void add_hwgenerator_randomness(const char *buffer, size_t count,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +1036 include/linux/pagemap.h
1031
1032 static inline void memcpy_page(struct page *dst_page, size_t dst_off,
1033 struct page *src_page, size_t src_off,
1034 size_t len)
1035 {
> 1036 char *dst = kmap_local_page(dst_page);
1037 char *src = kmap_local_page(src_page);
1038 memcpy(dst + dst_off, src + src_off, len);
1039 kunmap_local(src);
1040 kunmap_local(dst);
1041 }
1042
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
kernel test robot
build botRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
In reply to [email protected]I love your patch! Yet something to improve:
Hi,
I love your patch! Yet something to improve:
[auto build test ERROR on hch-configfs/for-next]
[also build test ERROR on linus/master v5.10-rc7]
[cannot apply to hnaz-linux-mm/master next-20201207]
[If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/ira-weiny-intel-com/Lift-memcpy_-to-from-_page-to-core/20201208-070017 base: git://git.infradead.org/users/hch/configfs.git for-next config: powerpc64-randconfig-r002-20201207 (attached as .config) compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project a2f922140f5380571fb74179f2bf622b3b925697)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# install powerpc64 cross compiling tool for clang build
# apt-get install binutils-powerpc64-linux-gnu
# https://github.com/0day-ci/linux/commit/23e6d3f08a315c6e70fde3d63a275c91e1dcb0ee
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review ira-weiny-intel-com/Lift-memcpy_-to-from-_page-to-core/20201208-070017 git checkout 23e6d3f08a315c6e70fde3d63a275c91e1dcb0ee
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc64
If you fix the issue, kindly add following tag as appropriate
All error/warnings (new ones prefixed by >>):
<scratch space>:223:1: note: expanded from here
__do_outsw
^
arch/powerpc/include/asm/io.h:545:58: note: expanded from macro '__do_outsw'
#define __do_outsw(p, b, n) writesw((PCI_IO_ADDR)_IO_BASE+(p),(b),(n))
~~~~~~~~~~~~~~~~~~~~~^
In file included from arch/powerpc/kernel/asm-offsets.c:23:
In file included from include/linux/suspend.h:5:
In file included from include/linux/swap.h:9:
In file included from include/linux/memcontrol.h:13:
In file included from include/linux/cgroup.h:26:
In file included from include/linux/kernel_stat.h:9:
In file included from include/linux/interrupt.h:11:
In file included from include/linux/hardirq.h:10:
In file included from arch/powerpc/include/asm/hardirq.h:6:
In file included from include/linux/irq.h:20:
In file included from include/linux/io.h:13:
In file included from arch/powerpc/include/asm/io.h:604:
arch/powerpc/include/asm/io-defs.h:53:1: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
DEF_PCI_AC_NORET(outsl, (unsigned long p, const void *b, unsigned long c),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/powerpc/include/asm/io.h:601:3: note: expanded from macro 'DEF_PCI_AC_NORET'
__do_##name al; \
^~~~~~~~~~~~~~
<scratch space>:225:1: note: expanded from here
__do_outsl
^
arch/powerpc/include/asm/io.h:546:58: note: expanded from macro '__do_outsl'
#define __do_outsl(p, b, n) writesl((PCI_IO_ADDR)_IO_BASE+(p),(b),(n))
~~~~~~~~~~~~~~~~~~~~~^
In file included from arch/powerpc/kernel/asm-offsets.c:23:
In file included from include/linux/suspend.h:5:
In file included from include/linux/swap.h:9:
In file included from include/linux/memcontrol.h:22:
In file included from include/linux/writeback.h:14:
In file included from include/linux/blk-cgroup.h:23:
In file included from include/linux/blkdev.h:14:
In file included from include/linux/pagemap.h:11:
include/linux/highmem.h:229:15: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
void *addr = kmap_local_page(page);
^
include/linux/highmem.h:229:15: note: did you mean 'kmap_to_page'?
include/linux/highmem.h:130:28: note: 'kmap_to_page' declared here
static inline struct page *kmap_to_page(void *addr)
^
include/linux/highmem.h:229:8: warning: incompatible integer to pointer conversion initializing 'void *' with an expression of type 'int' [-Wint-conversion]
void *addr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:231:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(addr);
^
include/linux/highmem.h:282:16: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
void *kaddr = kmap_local_page(page);
^
include/linux/highmem.h:282:8: warning: incompatible integer to pointer conversion initializing 'void *' with an expression of type 'int' [-Wint-conversion]
void *kaddr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:284:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(kaddr);
^
include/linux/highmem.h:291:16: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
void *kaddr = kmap_local_page(page);
^
include/linux/highmem.h:291:8: warning: incompatible integer to pointer conversion initializing 'void *' with an expression of type 'int' [-Wint-conversion]
void *kaddr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:301:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(kaddr);
^
include/linux/highmem.h:324:10: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
vfrom = kmap_local_page(from);
^
include/linux/highmem.h:324:8: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vfrom = kmap_local_page(from);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:325:6: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vto = kmap_local_page(to);
^ ~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:327:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(vto);
^
include/linux/highmem.h:339:10: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
vfrom = kmap_local_page(from);
^
include/linux/highmem.h:339:8: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vfrom = kmap_local_page(from);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:340:6: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vto = kmap_local_page(to);
^ ~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:342:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(vto);
^
In file included from arch/powerpc/kernel/asm-offsets.c:23:
In file included from include/linux/suspend.h:5:
In file included from include/linux/swap.h:9:
In file included from include/linux/memcontrol.h:22:
In file included from include/linux/writeback.h:14:
In file included from include/linux/blk-cgroup.h:23:
In file included from include/linux/blkdev.h:14:
>> include/linux/pagemap.h:1036:14: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *dst = kmap_local_page(dst_page);
^
>> include/linux/pagemap.h:1036:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *dst = kmap_local_page(dst_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1037:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *src = kmap_local_page(src_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/pagemap.h:1039:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(src);
^
include/linux/pagemap.h:1047:14: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *dst = kmap_local_page(dst_page);
^
include/linux/pagemap.h:1047:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *dst = kmap_local_page(dst_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1048:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *src = kmap_local_page(src_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1050:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(src);
^
include/linux/pagemap.h:1056:15: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *from = kmap_local_page(page);
^
include/linux/pagemap.h:1056:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *from = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1058:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(from);
^
include/linux/pagemap.h:1063:13: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *to = kmap_local_page(page);
^
include/linux/pagemap.h:1063:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *to = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1065:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(to);
^
include/linux/pagemap.h:1070:15: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *addr = kmap_local_page(page);
^
include/linux/pagemap.h:1070:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *addr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~ fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 warnings and 20 errors generated.
--
<scratch space>:223:1: note: expanded from here
__do_outsw
^
arch/powerpc/include/asm/io.h:545:58: note: expanded from macro '__do_outsw'
#define __do_outsw(p, b, n) writesw((PCI_IO_ADDR)_IO_BASE+(p),(b),(n))
~~~~~~~~~~~~~~~~~~~~~^
In file included from arch/powerpc/kernel/asm-offsets.c:23:
In file included from include/linux/suspend.h:5:
In file included from include/linux/swap.h:9:
In file included from include/linux/memcontrol.h:13:
In file included from include/linux/cgroup.h:26:
In file included from include/linux/kernel_stat.h:9:
In file included from include/linux/interrupt.h:11:
In file included from include/linux/hardirq.h:10:
In file included from arch/powerpc/include/asm/hardirq.h:6:
In file included from include/linux/irq.h:20:
In file included from include/linux/io.h:13:
In file included from arch/powerpc/include/asm/io.h:604:
arch/powerpc/include/asm/io-defs.h:53:1: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
DEF_PCI_AC_NORET(outsl, (unsigned long p, const void *b, unsigned long c),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/powerpc/include/asm/io.h:601:3: note: expanded from macro 'DEF_PCI_AC_NORET'
__do_##name al; \
^~~~~~~~~~~~~~
<scratch space>:225:1: note: expanded from here
__do_outsl
^
arch/powerpc/include/asm/io.h:546:58: note: expanded from macro '__do_outsl'
#define __do_outsl(p, b, n) writesl((PCI_IO_ADDR)_IO_BASE+(p),(b),(n))
~~~~~~~~~~~~~~~~~~~~~^
In file included from arch/powerpc/kernel/asm-offsets.c:23:
In file included from include/linux/suspend.h:5:
In file included from include/linux/swap.h:9:
In file included from include/linux/memcontrol.h:22:
In file included from include/linux/writeback.h:14:
In file included from include/linux/blk-cgroup.h:23:
In file included from include/linux/blkdev.h:14:
In file included from include/linux/pagemap.h:11:
include/linux/highmem.h:229:15: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
void *addr = kmap_local_page(page);
^
include/linux/highmem.h:229:15: note: did you mean 'kmap_to_page'?
include/linux/highmem.h:130:28: note: 'kmap_to_page' declared here
static inline struct page *kmap_to_page(void *addr)
^
include/linux/highmem.h:229:8: warning: incompatible integer to pointer conversion initializing 'void *' with an expression of type 'int' [-Wint-conversion]
void *addr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:231:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(addr);
^
include/linux/highmem.h:282:16: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
void *kaddr = kmap_local_page(page);
^
include/linux/highmem.h:282:8: warning: incompatible integer to pointer conversion initializing 'void *' with an expression of type 'int' [-Wint-conversion]
void *kaddr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:284:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(kaddr);
^
include/linux/highmem.h:291:16: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
void *kaddr = kmap_local_page(page);
^
include/linux/highmem.h:291:8: warning: incompatible integer to pointer conversion initializing 'void *' with an expression of type 'int' [-Wint-conversion]
void *kaddr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:301:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(kaddr);
^
include/linux/highmem.h:324:10: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
vfrom = kmap_local_page(from);
^
include/linux/highmem.h:324:8: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vfrom = kmap_local_page(from);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:325:6: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vto = kmap_local_page(to);
^ ~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:327:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(vto);
^
include/linux/highmem.h:339:10: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
vfrom = kmap_local_page(from);
^
include/linux/highmem.h:339:8: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vfrom = kmap_local_page(from);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:340:6: warning: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]
vto = kmap_local_page(to);
^ ~~~~~~~~~~~~~~~~~~~
include/linux/highmem.h:342:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(vto);
^
In file included from arch/powerpc/kernel/asm-offsets.c:23:
In file included from include/linux/suspend.h:5:
In file included from include/linux/swap.h:9:
In file included from include/linux/memcontrol.h:22:
In file included from include/linux/writeback.h:14:
In file included from include/linux/blk-cgroup.h:23:
In file included from include/linux/blkdev.h:14:
>> include/linux/pagemap.h:1036:14: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *dst = kmap_local_page(dst_page);
^
>> include/linux/pagemap.h:1036:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *dst = kmap_local_page(dst_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1037:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *src = kmap_local_page(src_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/pagemap.h:1039:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(src);
^
include/linux/pagemap.h:1047:14: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *dst = kmap_local_page(dst_page);
^
include/linux/pagemap.h:1047:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *dst = kmap_local_page(dst_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1048:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *src = kmap_local_page(src_page);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1050:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(src);
^
include/linux/pagemap.h:1056:15: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *from = kmap_local_page(page);
^
include/linux/pagemap.h:1056:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *from = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1058:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(from);
^
include/linux/pagemap.h:1063:13: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *to = kmap_local_page(page);
^
include/linux/pagemap.h:1063:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *to = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~
include/linux/pagemap.h:1065:2: error: implicit declaration of function 'kunmap_local' [-Werror,-Wimplicit-function-declaration]
kunmap_local(to);
^
include/linux/pagemap.h:1070:15: error: implicit declaration of function 'kmap_local_page' [-Werror,-Wimplicit-function-declaration]
char *addr = kmap_local_page(page);
^
include/linux/pagemap.h:1070:8: warning: incompatible integer to pointer conversion initializing 'char *' with an expression of type 'int' [-Wint-conversion]
char *addr = kmap_local_page(page);
^ ~~~~~~~~~~~~~~~~~~~~~ fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 warnings and 20 errors generated.
make[2]: *** [scripts/Makefile.build:117: arch/powerpc/kernel/asm-offsets.s] Error 1 make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1200: prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:185: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
vim +/kmap_local_page +1036 include/linux/pagemap.h
1031
1032 static inline void memcpy_page(struct page *dst_page, size_t dst_off,
1033 struct page *src_page, size_t src_off,
1034 size_t len)
1035 {
> 1036 char *dst = kmap_local_page(dst_page); 1037 char *src = kmap_local_page(src_page); 1038 memcpy(dst + dst_off, src + src_off, len); > 1039 kunmap_local(src);
1040 kunmap_local(dst);
1041 }
1042
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
In reply to [email protected]Quoted 8 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
Placing these functions in '
highmem.h' is suboptimal especially with the changes being proposed in the functionality of kmap. From a caller perspective including/using 'highmem.h' implies that the functions defined in that header are only required when highmem is in use which is increasingly not the case with modern processors. Some headers likemm.horstring.hseem ok but don't really portray the functionality well. 'pagemap.h', on the other hand, makes sense and is already included in many of the places we want to convert.
pagemap.h is for the page cache. It's not for "random page functionality". Yes, I know it's badly named. No, I don't want to rename it. These helpers should go in highmem.h along with zero_user().
Re: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 10 lines · Matthew Wilcox
Quoted 8 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
Placing these functions in '
highmem.h' is suboptimal especially with the changes being proposed in the functionality of kmap. From a caller perspective including/using 'highmem.h' implies that the functions defined in that header are only required when highmem is in use which is increasingly not the case with modern processors. Some headers likemm.horstring.hseem ok but don't really portray the functionality well. 'pagemap.h', on the other hand, makes sense and is already included in many of the places we want to convert.
Quoted 3 lines
pagemap.his for the page cache. It's not for "random page functionality". Yes, I know it's badly named. No, I don't want to rename it. These helpers should go inhighmem.halong withzero_user().
I could have sworn you suggested pagemap.h. But I can't find the evidence on
lore. :-/ hehehe...
In the end the code does not care. I have a distaste for highmem.h because it is no longer for 'high memory'. And I think a number of driver writers who are targeting 64bit platforms just don't care any more. So as we head toward memory not being mapped by the kernel for other reasons I think highmem needs to be 'rebranded' if not renamed.
Ira
Matthew Wilcox
maintainerRe: [PATCH V2 2/2] mm/highmem: Lift memcpy_[to|from]_page to core
Quoted 15 lines · Ira Weiny
Quoted 10 lines · Matthew Wilcox
Quoted 8 lines · On Mon, Dec 07, 2020 at 02:57:03PM -0800, [email protected] wrote:
Placing these functions in '
highmem.h' is suboptimal especially with the changes being proposed in the functionality of kmap. From a caller perspective including/using 'highmem.h' implies that the functions defined in that header are only required when highmem is in use which is increasingly not the case with modern processors. Some headers likemm.horstring.hseem ok but don't really portray the functionality well. 'pagemap.h', on the other hand, makes sense and is already included in many of the places we want to convert.Quoted 3 lines
pagemap.his for the page cache. It's not for "random page functionality". Yes, I know it's badly named. No, I don't want to rename it. These helpers should go inhighmem.halong withzero_user().
Quoted 8 lines
I could have sworn you suggested
pagemap.h. But I can't find the evidence on
lore. :-/ hehehe...In the end the code does not care. I have a distaste for
highmem.hbecause it is no longer for 'high memory'. And I think a number of driver writers who are targeting 64bit platforms just don't care any more. So as we head toward memory not being mapped by the kernel for other reasons I think highmem needs to be 'rebranded' if not renamed.
Rename highmem.h to kmap.h?