All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH V2 08/12] fs/xfs: Add lock/unlock mode to xfs
Date: Sat, 11 Jan 2020 22:49:49 +0800	[thread overview]
Message-ID: <202001112114.Kq8pneJn%lkp@intel.com> (raw)
In-Reply-To: <20200110192942.25021-9-ira.weiny@intel.com>

[-- Attachment #1: Type: text/plain, Size: 4002 bytes --]

Hi,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on xfs-linux/for-next]
[also build test ERROR on linux/master linus/master v5.5-rc5]
[cannot apply to djwong-xfs/djwong-devel next-20200110]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/ira-weiny-intel-com/Enable-per-file-directory-DAX-operations-V2/20200111-095526
base:   https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next
config: x86_64-lkp (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   fs/xfs/xfs_inode.c: In function 'xfs_isilocked':
>> fs/xfs/xfs_inode.c:394:43: error: macro "percpu_rwsem_is_held" passed 2 arguments, but takes just 1
        percpu_rwsem_is_held(&ip->i_dax_sem, 0);
                                              ^
>> fs/xfs/xfs_inode.c:394:5: error: 'percpu_rwsem_is_held' undeclared (first use in this function); did you mean 'percpu_ref_is_zero'?
        percpu_rwsem_is_held(&ip->i_dax_sem, 0);
        ^~~~~~~~~~~~~~~~~~~~
        percpu_ref_is_zero
   fs/xfs/xfs_inode.c:394:5: note: each undeclared identifier is reported only once for each function it appears in
>> fs/xfs/xfs_inode.c:395:26: error: passing argument 1 of 'rwsem_is_locked' from incompatible pointer type [-Werror=incompatible-pointer-types]
      return rwsem_is_locked(&ip->i_dax_sem);
                             ^
   In file included from include/linux/mm_types.h:11:0,
                    from include/linux/mmzone.h:21,
                    from include/linux/gfp.h:6,
                    from include/linux/xarray.h:14,
                    from include/linux/radix-tree.h:18,
                    from include/linux/fs.h:15,
                    from include/linux/iversion.h:5,
                    from fs/xfs/xfs_inode.c:6:
   include/linux/rwsem.h:63:19: note: expected 'struct rw_semaphore *' but argument is of type 'struct percpu_rw_semaphore *'
    static inline int rwsem_is_locked(struct rw_semaphore *sem)
                      ^~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/percpu_rwsem_is_held +394 fs/xfs/xfs_inode.c

   365	
   366	#if defined(DEBUG) || defined(XFS_WARN)
   367	int
   368	xfs_isilocked(
   369		xfs_inode_t		*ip,
   370		uint			lock_flags)
   371	{
   372		if (lock_flags & (XFS_ILOCK_EXCL|XFS_ILOCK_SHARED)) {
   373			if (!(lock_flags & XFS_ILOCK_SHARED))
   374				return !!ip->i_lock.mr_writer;
   375			return rwsem_is_locked(&ip->i_lock.mr_lock);
   376		}
   377	
   378		if (lock_flags & (XFS_MMAPLOCK_EXCL|XFS_MMAPLOCK_SHARED)) {
   379			if (!(lock_flags & XFS_MMAPLOCK_SHARED))
   380				return !!ip->i_mmaplock.mr_writer;
   381			return rwsem_is_locked(&ip->i_mmaplock.mr_lock);
   382		}
   383	
   384		if (lock_flags & (XFS_IOLOCK_EXCL|XFS_IOLOCK_SHARED)) {
   385			if (!(lock_flags & XFS_IOLOCK_SHARED))
   386				return !debug_locks ||
   387					lockdep_is_held_type(&VFS_I(ip)->i_rwsem, 0);
   388			return rwsem_is_locked(&VFS_I(ip)->i_rwsem);
   389		}
   390	
   391		if (lock_flags & (XFS_DAX_EXCL|XFS_DAX_SHARED)) {
   392			if (!(lock_flags & XFS_DAX_SHARED))
   393				return !debug_locks ||
 > 394					percpu_rwsem_is_held(&ip->i_dax_sem, 0);
 > 395			return rwsem_is_locked(&ip->i_dax_sem);
   396		}
   397	
   398		ASSERT(0);
   399		return 0;
   400	}
   401	#endif
   402	

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 28789 bytes --]

  reply	other threads:[~2020-01-11 14:49 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 19:29 [RFC PATCH V2 00/12] Enable per-file/directory DAX operations V2 ira.weiny
2020-01-10 19:29 ` [RFC PATCH V2 01/12] fs/stat: Define DAX statx attribute ira.weiny
2020-01-15 11:37   ` Jan Kara
2020-01-15 17:38     ` Darrick J. Wong
2020-01-15 19:45       ` Ira Weiny
2020-01-15 20:10         ` Dan Williams
2020-01-15 22:38           ` Ira Weiny
2020-01-16  5:39             ` Darrick J. Wong
2020-01-16  6:05               ` Dan Williams
2020-01-16  6:18                 ` Darrick J. Wong
2020-01-16  6:25                   ` Dan Williams
2020-01-18  9:11                 ` Dave Chinner
2020-01-16 17:55               ` Ira Weiny
2020-01-16 18:04                 ` Darrick J. Wong
2020-01-16 18:52                   ` Ira Weiny
2020-01-16 22:19                     ` Darrick J. Wong
2020-01-17 11:58                     ` Jan Kara
2020-01-10 19:29 ` [RFC PATCH V2 02/12] fs/xfs: Isolate the physical DAX flag from effective ira.weiny
2020-01-10 19:29 ` [RFC PATCH V2 03/12] fs/xfs: Separate functionality of xfs_inode_supports_dax() ira.weiny
2020-01-10 19:29 ` [RFC PATCH V2 04/12] fs/xfs: Clean up DAX support check ira.weiny
2020-01-10 19:29 ` [RFC PATCH V2 05/12] fs: remove unneeded IS_DAX() check ira.weiny
2020-01-16  9:38   ` Jan Kara
2020-01-16 18:47     ` Ira Weiny
2020-01-10 19:29 ` [RFC PATCH V2 06/12] fs/xfs: Check if the inode supports DAX under lock ira.weiny
2020-01-10 19:29 ` [RFC PATCH V2 07/12] fs: Add locking for a dynamic inode 'mode' ira.weiny
2020-01-13 22:12   ` Darrick J. Wong
2020-01-14  0:20     ` Ira Weiny
2020-01-14  1:03       ` Darrick J. Wong
2020-01-15 19:08         ` Ira Weiny
2020-01-16  5:40           ` Darrick J. Wong
2020-01-16 18:54             ` Ira Weiny
2020-01-10 19:29 ` [RFC PATCH V2 08/12] fs/xfs: Add lock/unlock mode to xfs ira.weiny
2020-01-11 14:49   ` kbuild test robot [this message]
2020-01-13 22:19   ` Darrick J. Wong
2020-01-14  0:35     ` Ira Weiny
2020-01-15  0:57       ` Ira Weiny
2020-01-15 23:52     ` Ira Weiny
2020-01-16  9:24   ` Jan Kara
2020-01-16 19:12     ` Ira Weiny
2020-01-10 19:29 ` [RFC PATCH V2 09/12] fs: Prevent mode change if file is mmap'ed ira.weiny
2020-01-13 22:22   ` Darrick J. Wong
2020-01-14  0:46     ` Ira Weiny
2020-01-14  1:30       ` Darrick J. Wong
2020-01-14 17:53         ` Ira Weiny
2020-01-15 11:34           ` Jan Kara
2020-01-15 18:24             ` Ira Weiny
2020-01-15 10:21   ` David Laight
2020-01-15 17:53     ` Ira Weiny
2020-01-10 19:29 ` [RFC PATCH V2 10/12] fs/xfs: Fix truncate up ira.weiny
2020-01-13 22:27   ` Darrick J. Wong
2020-01-14  0:40     ` Ira Weiny
2020-01-14  1:14       ` Darrick J. Wong
2020-01-14 19:00         ` Ira Weiny
2020-01-14 19:39           ` Ira Weiny
2020-01-10 19:29 ` [RFC PATCH V2 11/12] fs/xfs: Clean up locking in dax invalidate ira.weiny
2020-01-10 19:29 ` [RFC PATCH V2 12/12] fs/xfs: Allow toggle of effective DAX flag ira.weiny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202001112114.Kq8pneJn%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.