From: kernel test robot <lkp@intel.com>
To: kaixuxia@tencent.com, frankjpliu@tencent.com, kasong@tencent.com,
sagazchen@tencent.com, kernelxing@tencent.com,
aurelianliu@tencent.com, deshengwu@tencent.com,
flyingpeng@tencent.com, jingqunli@tencent.com,
jason.zeng@intel.com, wu.zheng@intel.com, yingbao.jia@intel.com,
pei.p.jia@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [opencloudos:next 13/98] kernel/sysctl.c:1033:45: sparse: sparse: incorrect type in argument 3 (different address spaces)
Date: Tue, 29 Oct 2024 11:09:28 +0800 [thread overview]
Message-ID: <202410291137.RSSvrKAi-lkp@intel.com> (raw)
tree: https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git next
head: ce9f9d823a41831d622fa11e29c3d620c044f51b
commit: 95c98461d1dce7fd1d25f055c88ad639b0e3b7d7 [13/98] sysrq: add ALT+LEFTCTRL to trigger crash dump
config: x86_64-randconfig-122-20241029 (https://download.01.org/0day-ci/archive/20241029/202410291137.RSSvrKAi-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241029/202410291137.RSSvrKAi-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/202410291137.RSSvrKAi-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/sysctl.c:1033:45: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected void *buffer @@ got void [noderef] __user *buffer @@
kernel/sysctl.c:1033:45: sparse: expected void *buffer
kernel/sysctl.c:1033:45: sparse: got void [noderef] __user *buffer
kernel/sysctl.c:1791:35: sparse: sparse: incorrect type in initializer (incompatible argument 3 (different address spaces)) @@ expected int ( [usertype] *proc_handler )( ... ) @@ got int ( * )( ... ) @@
kernel/sysctl.c:1791:35: sparse: expected int ( [usertype] *proc_handler )( ... )
kernel/sysctl.c:1791:35: sparse: got int ( * )( ... )
kernel/sysctl.c:312:66: sparse: sparse: self-comparison always evaluates to false
vim +1033 kernel/sysctl.c
1026
1027 static int sysrq_use_leftctrl_sysctl_handler(struct ctl_table *table, int write,
1028 void __user *buffer, size_t *lenp,
1029 loff_t *ppos)
1030 {
1031 int error;
1032
> 1033 error = proc_dointvec(table, write, buffer, lenp, ppos);
1034 if (error)
1035 return error;
1036
1037 if (write)
1038 sysrq_toggle_sysrq_key(__sysrq_use_leftctrl);
1039
1040 return 0;
1041 }
1042 #endif
1043
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-10-29 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 3:09 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-30 12:39 [opencloudos:next 13/98] kernel/sysctl.c:1033:45: sparse: sparse: incorrect type in argument 3 (different address spaces) kernel test robot
2024-03-04 10:48 kernel test robot
2024-03-03 18:58 kernel test robot
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=202410291137.RSSvrKAi-lkp@intel.com \
--to=lkp@intel.com \
--cc=aurelianliu@tencent.com \
--cc=deshengwu@tencent.com \
--cc=flyingpeng@tencent.com \
--cc=frankjpliu@tencent.com \
--cc=jason.zeng@intel.com \
--cc=jingqunli@tencent.com \
--cc=kaixuxia@tencent.com \
--cc=kasong@tencent.com \
--cc=kernelxing@tencent.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pei.p.jia@intel.com \
--cc=sagazchen@tencent.com \
--cc=wu.zheng@intel.com \
--cc=yingbao.jia@intel.com \
/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.