From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-desktop 1/1] kernel/locking/rwsem.c:1651:9: error: implicit declaration of function 'trace_android_vh_rwsem_write_finished'; did you mean 'trace_android_vh_rwsem_write_wait_finish'?
Date: Thu, 13 Aug 2026 09:02:24 +0800 [thread overview]
Message-ID: <202608130815.rxMhNnSQ-lkp@intel.com> (raw)
Hi JianMin,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12-desktop
head: 24c37396da197463e1ff2bc69bb789e34dacad53
commit: 78cf7a145c200d185e2370c712abd8235d1bd5aa [1/1] ANDROID: rwsem: Add vendor hook to the rw-semaphore
config: x86_64-buildonly-randconfig-004-20260813 (https://download.01.org/0day-ci/archive/20260813/202608130815.rxMhNnSQ-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260813/202608130815.rxMhNnSQ-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/202608130815.rxMhNnSQ-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/locking/rwsem.c: In function 'up_write':
>> kernel/locking/rwsem.c:1651:9: error: implicit declaration of function 'trace_android_vh_rwsem_write_finished'; did you mean 'trace_android_vh_rwsem_write_wait_finish'? [-Wimplicit-function-declaration]
1651 | trace_android_vh_rwsem_write_finished(sem);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| trace_android_vh_rwsem_write_wait_finish
vim +1651 kernel/locking/rwsem.c
1644
1645 /*
1646 * release a write lock
1647 */
1648 void up_write(struct rw_semaphore *sem)
1649 {
1650 rwsem_release(&sem->dep_map, _RET_IP_);
> 1651 trace_android_vh_rwsem_write_finished(sem);
1652 __up_write(sem);
1653 }
1654 EXPORT_SYMBOL(up_write);
1655
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-13 1:03 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=202608130815.rxMhNnSQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.