Re: [PATCH 2/4] ubifs: Implement RENAME_WHITEOUT

[kbuild test robot]

Hi Richard,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc6]
[cannot apply to next-20160913]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Richard-Weinberger/ubifs-Implement-O_TMPFILE/20160913-222814
config: x86_64-randconfig-x013-201637 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   fs/ubifs/dir.c: In function 'lock_4_inodes':
>> fs/ubifs/dir.c:1041:53: error: 'WB_MUTEX_4' undeclared (first use in this function)
      mutex_lock_nested(&ubifs_inode(inode4)->ui_mutex, WB_MUTEX_4);
                                                        ^~~~~~~~~~
   fs/ubifs/dir.c:1041:53: note: each undeclared identifier is reported only once for each function it appears in

vim +/WB_MUTEX_4 +1041 fs/ubifs/dir.c

  1035		mutex_lock_nested(&ubifs_inode(inode1)->ui_mutex, WB_MUTEX_1);
  1036		if (inode2 != inode1)
  1037			mutex_lock_nested(&ubifs_inode(inode2)->ui_mutex, WB_MUTEX_2);
  1038		if (inode3)
  1039			mutex_lock_nested(&ubifs_inode(inode3)->ui_mutex, WB_MUTEX_3);
  1040		if (inode4)
> 1041			mutex_lock_nested(&ubifs_inode(inode4)->ui_mutex, WB_MUTEX_4);
  1042	}
  1043	
  1044	/**

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

Attachment: .config.gz
Description: Binary data