From: kernel test robot <lkp@intel.com>
To: Alex Markuze <amarkuze@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, ceph-devel@vger.kernel.org
Subject: [ceph-client:tls_logger 13/13] net/ceph/ceph_san.c:25:39: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Fri, 14 Feb 2025 01:45:59 +0800 [thread overview]
Message-ID: <202502140148.QryPfsF2-lkp@intel.com> (raw)
tree: https://github.com/ceph/ceph-client.git tls_logger
head: cd1e899feeb6a7da55cbb74b9245c8bbb77f82ba
commit: cd1e899feeb6a7da55cbb74b9245c8bbb77f82ba [13/13] cephsun: using a dynamic buffer allocation
config: alpha-randconfig-r133-20250213 (https://download.01.org/0day-ci/archive/20250214/202502140148.QryPfsF2-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250214/202502140148.QryPfsF2-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/202502140148.QryPfsF2-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
net/ceph/ceph_san.c:188:39: sparse: sparse: no newline at end of file
net/ceph/ceph_san.c:24:39: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct ceph_san_tls_logger * @@
net/ceph/ceph_san.c:24:39: sparse: expected void const [noderef] __percpu *__vpp_verify
net/ceph/ceph_san.c:24:39: sparse: got struct ceph_san_tls_logger *
>> net/ceph/ceph_san.c:25:39: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct cephsan_pagefrag * @@
net/ceph/ceph_san.c:25:39: sparse: expected void const [noderef] __percpu *__vpp_verify
net/ceph/ceph_san.c:25:39: sparse: got struct cephsan_pagefrag *
net/ceph/ceph_san.c:54:23: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct ceph_san_tls_logger * @@
net/ceph/ceph_san.c:54:23: sparse: expected void const [noderef] __percpu *__vpp_verify
net/ceph/ceph_san.c:54:23: sparse: got struct ceph_san_tls_logger *
net/ceph/ceph_san.c:72:23: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct ceph_san_tls_logger * @@
net/ceph/ceph_san.c:72:23: sparse: expected void const [noderef] __percpu *__vpp_verify
net/ceph/ceph_san.c:72:23: sparse: got struct ceph_san_tls_logger *
net/ceph/ceph_san.c:82:22: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got struct cephsan_pagefrag * @@
net/ceph/ceph_san.c:82:22: sparse: expected void const [noderef] __percpu *__vpp_verify
net/ceph/ceph_san.c:82:22: sparse: got struct cephsan_pagefrag *
vim +25 net/ceph/ceph_san.c
15
16
17 static inline void *cephsan_pagefrag_get_ptr(struct cephsan_pagefrag *pf, u64 val);
18 /* The definitions for struct ceph_san_log_entry and struct ceph_san_tls_logger
19 * have been moved to cephsan.h (under CONFIG_DEBUG_FS) to avoid duplication.
20 */
21
22 void log_cephsan(char *buf) {
23 /* Use the per-core TLS logger */
24 struct ceph_san_tls_logger *tls = this_cpu_ptr(&ceph_san_tls);
> 25 struct cephsan_pagefrag *pf = this_cpu_ptr(&ceph_san_pagefrag);
26
27 int head_idx = tls->head_idx++ & (CEPH_SAN_MAX_LOGS - 1);
28 int pre_len = tls->logs[head_idx].len;
29 tls->logs[head_idx].pid = current->pid;
30 tls->logs[head_idx].ts = jiffies;
31 memcpy(tls->logs[head_idx].comm, current->comm, TASK_COMM_LEN);
32
33 cephsan_pagefrag_free(pf, pre_len);
34
35 int len = strlen(buf);
36 u64 buf_idx = cephsan_pagefrag_alloc(pf, len);
37 if (buf_idx) {
38 tls->logs[head_idx].len = len;
39 tls->logs[head_idx].buf = cephsan_pagefrag_get_ptr(pf, buf_idx);
40 memcpy(tls->logs[head_idx].buf, buf, len);
41 }
42 }
43 EXPORT_SYMBOL(log_cephsan);
44
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-13 17:46 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=202502140148.QryPfsF2-lkp@intel.com \
--to=lkp@intel.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--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.