linux-next: build failure after merge of the mm tree

[Stephen Rothwell]

Hi all,

After merging the mm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

fs/proc/task_mmu.c: In function 'get_vma_snapshow':
fs/proc/task_mmu.c:145:19: error: 'struct vm_area_struct' has no member named 'anon_name'; did you mean 'anon_vma'?
  145 |         if (copy->anon_name && !anon_vma_name_get_rcu(copy))
      |                   ^~~~~~~~~
      |                   anon_vma
fs/proc/task_mmu.c:161:19: error: 'struct vm_area_struct' has no member named 'anon_name'; did you mean 'anon_vma'?
  161 |         if (copy->anon_name)
      |                   ^~~~~~~~~
      |                   anon_vma
fs/proc/task_mmu.c:162:41: error: 'struct vm_area_struct' has no member named 'anon_name'; did you mean 'anon_vma'?
  162 |                 anon_vma_name_put(copy->anon_name);
      |                                         ^~~~~~~~~
      |                                         anon_vma
fs/proc/task_mmu.c: In function 'put_vma_snapshot':
fs/proc/task_mmu.c:174:18: error: 'struct vm_area_struct' has no member named 'anon_name'; did you mean 'anon_vma'?
  174 |         if (vma->anon_name)
      |                  ^~~~~~~~~
      |                  anon_vma
fs/proc/task_mmu.c:175:40: error: 'struct vm_area_struct' has no member named 'anon_name'; did you mean 'anon_vma'?
  175 |                 anon_vma_name_put(vma->anon_name);
      |                                        ^~~~~~~~~
      |                                        anon_vma

Caused by commit

  786cebbd51a4 ("mm/maps: read proc/pid/maps under RCU")

from the mm-unstable branch.

This build does not have CONFIG_ANON_VMA_NAME set.

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

Attachment: pgpC60_K2c1Bd.pgp
Description: OpenPGP digital signature