All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:afs-next 40/43] fs/afs/callback.c:82:6: error: invalid output size for constraint '+q'
Date: Wed, 13 Dec 2023 18:48:16 +0800	[thread overview]
Message-ID: <202312131803.JZPzoKWV-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git afs-next
head:   f1302568cc65d3fdd85e6413688779e5235f4e2b
commit: b8f604776e35dd984fbf93f49276543461cbbb22 [40/43] afs: Overhaul invalidation handling to better support RO volumes
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20231213/202312131803.JZPzoKWV-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231213/202312131803.JZPzoKWV-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312131803.JZPzoKWV-lkp@intel.com/

All errors (new ones prefixed by >>):

>> fs/afs/callback.c:82:6: error: invalid output size for constraint '+q'
           if (xchg(&vnode->cb_expires_at, AFS_NO_CB_PROMISE) != AFS_NO_CB_PROMISE) {
               ^
   include/linux/atomic/atomic-instrumented.h:4716:2: note: expanded from macro 'xchg'
           raw_xchg(__ai_ptr, __VA_ARGS__); \
           ^
   include/linux/atomic/atomic-arch-fallback.h:12:18: note: expanded from macro 'raw_xchg'
   #define raw_xchg arch_xchg
                    ^
   arch/x86/include/asm/cmpxchg.h:78:27: note: expanded from macro 'arch_xchg'
   #define arch_xchg(ptr, v)       __xchg_op((ptr), (v), xchg, "")
                                   ^
   arch/x86/include/asm/cmpxchg.h:48:19: note: expanded from macro '__xchg_op'
                                         : "+q" (__ret), "+m" (*(ptr))     \
                                                 ^
   1 error generated.
--
>> fs/afs/rotate.c:62:7: error: invalid output size for constraint '+q'
                   if (xchg(&vnode->cb_expires_at, AFS_NO_CB_PROMISE) != AFS_NO_CB_PROMISE)
                       ^
   include/linux/atomic/atomic-instrumented.h:4716:2: note: expanded from macro 'xchg'
           raw_xchg(__ai_ptr, __VA_ARGS__); \
           ^
   include/linux/atomic/atomic-arch-fallback.h:12:18: note: expanded from macro 'raw_xchg'
   #define raw_xchg arch_xchg
                    ^
   arch/x86/include/asm/cmpxchg.h:78:27: note: expanded from macro 'arch_xchg'
   #define arch_xchg(ptr, v)       __xchg_op((ptr), (v), xchg, "")
                                   ^
   arch/x86/include/asm/cmpxchg.h:48:19: note: expanded from macro '__xchg_op'
                                         : "+q" (__ret), "+m" (*(ptr))     \
                                                 ^
   1 error generated.


vim +82 fs/afs/callback.c

    73	
    74	/*
    75	 * actually break a callback
    76	 */
    77	void __afs_break_callback(struct afs_vnode *vnode, enum afs_cb_break_reason reason)
    78	{
    79		_enter("");
    80	
    81		clear_bit(AFS_VNODE_NEW_CONTENT, &vnode->flags);
  > 82		if (xchg(&vnode->cb_expires_at, AFS_NO_CB_PROMISE) != AFS_NO_CB_PROMISE) {
    83			vnode->cb_break++;
    84			vnode->cb_v_check = atomic_read(&vnode->volume->cb_v_break);
    85			afs_clear_permits(vnode);
    86	
    87			if (vnode->lock_state == AFS_VNODE_LOCK_WAITING_FOR_CB)
    88				afs_lock_may_be_available(vnode);
    89	
    90			if (reason != afs_cb_break_for_deleted &&
    91			    vnode->status.type == AFS_FTYPE_FILE &&
    92			    atomic_read(&vnode->cb_nr_mmap))
    93				queue_work(system_unbound_wq, &vnode->cb_work);
    94	
    95			trace_afs_cb_break(&vnode->fid, vnode->cb_break, reason, true);
    96		} else {
    97			trace_afs_cb_break(&vnode->fid, vnode->cb_break, reason, false);
    98		}
    99	}
   100	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-12-13 10:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202312131803.JZPzoKWV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.