Hi all,
Looks like I'm still carrying patch "mm: distinguish CMA and MOVABLE
isolation in has_unmovable_pages" from Michal [1] for commit e1d753dff0fa
("mm: drop migrate type checks from has_unmovable_pages") and Linux next
has been broken for CMA for few weeks now as noted in the discussion
also at [1].
What's the status of this regression? How come it's been known
broken for two weeks and still not fixed or reverted in next?
This is clearly is not suitable for "wider testing" ;)
For reference, the symptoms I'm seeing is that at least loadable
modules using fail to work CMA produce the following errors:
# dmesg | grep -B1 cma
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 16 MiB at 0xbe800000
--
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 997000K/1046528K available (9216K kernel code, 815K
rwdata, 2464K rodata, 1024K init, 7558K bss, 33144K reserved, 16384K
cma-reserved, 243712K highmem)
--
[ 22.436920] twl_rtc 48070000.i2c:twl@48:rtc: rtc core: registered
48070000.i2c:twl@48:rtc as rtc0
[ 23.593933] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -16
--
[ 24.768920] ehci-omap 4a064c00.ehci: new USB bus registered, assigned bus
number 1
[ 24.828338] cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -16
--
[ 27.030517] DSS: OMAP DSS rev 4.0
[ 27.068237] cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -16
--
[ 27.651489] random: crng init done
[ 27.738494] cma: cma_alloc: alloc failed, req-size: 129 pages, ret: -16
Regards,
Tony
[1] https://lkml.org/lkml/2017/10/19/364
