- Kernel - mailweb.openeuler.org

[openeuler:OLK-6.6 3534/3534] kernel/sched/psi.c:894:13: warning: 'task_is_in_psi_v1' defined but not used
by kernel test robot 11 Dec '25

11 Dec '25

tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 423fccda72fc2b78107cc119a1755d968c2c36de commit: 2dfc29e742a07863c2426aea03d5c2c97b558b9d [3534/3534] sched/psi: Export cgroup psi from cgroupv2 to cgroupv1 config: x86_64-buildonly-randconfig-002-20251211 (https://download.01.org/0day-ci/archive/20251211/202512111054.dK8iS8qQ-lkp@…) 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/20251211/202512111054.dK8iS8qQ-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512111054.dK8iS8qQ-lkp@intel.com/ All warnings (new ones prefixed by >>): In file included from kernel/sched/build_utility.c:97: >> kernel/sched/psi.c:894:13: warning: 'task_is_in_psi_v1' defined but not used [-Wunused-function] 894 | static bool task_is_in_psi_v1(void) | ^~~~~~~~~~~~~~~~~ vim +/task_is_in_psi_v1 +894 kernel/sched/psi.c 884 885 #if defined(CONFIG_CGROUP_CPUACCT) && defined(CONFIG_PSI_CGROUP_V1) 886 static bool task_is_in_psi_v1(void) 887 { 888 if (static_branch_likely(&psi_v1_disabled)) 889 return false; 890 891 return !cgroup_subsys_on_dfl(cpuacct_cgrp_subsys); 892 } 893 #else > 894 static bool task_is_in_psi_v1(void) 895 { 896 return false; 897 } 898 #endif 899 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[openeuler:OLK-6.6 3508/3508] drivers/ub/urma/ubcore/ubcm/ubmad_datapath.c:141:22: sparse: sparse: symbol 'ubmad_create_rt_work' was not declared. Should it be static?
by kernel test robot 11 Dec '25

11 Dec '25

Hi Wen, First bad commit (maybe != root cause): tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 423fccda72fc2b78107cc119a1755d968c2c36de commit: ea9d81b3942d8f0336b9207b594a748e20ec16dd [3508/3508] ubcore: add ubcore_umem and ubcore_tp implementations config: arm64-randconfig-r112-20251210 (https://download.01.org/0day-ci/archive/20251211/202512111041.BvyrUXKy-lkp@…) compiler: aarch64-linux-gcc (GCC) 13.4.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512111041.BvyrUXKy-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512111041.BvyrUXKy-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/ub/urma/ubcore/ubcm/ubmad_datapath.c:141:22: sparse: sparse: symbol 'ubmad_create_rt_work' was not declared. Should it be static? >> drivers/ub/urma/ubcore/ubcm/ubmad_datapath.c:530:5: sparse: sparse: symbol 'ubmad_post_send_conn_ack' was not declared. Should it be static? >> drivers/ub/urma/ubcore/ubcm/ubmad_datapath.c:550:5: sparse: sparse: symbol 'ubmad_repost_send_conn_data' was not declared. Should it be static? >> drivers/ub/urma/ubcore/ubcm/ubmad_datapath.c:757:6: sparse: sparse: symbol 'ubmad_process_rx_msn' was not declared. Should it be static? vim +/ubmad_create_rt_work +141 drivers/ub/urma/ubcore/ubcm/ubmad_datapath.c e34a52d4eed891 Wen Chen 2025-11-12 140 e34a52d4eed891 Wen Chen 2025-11-12 @141 struct ubmad_rt_work *ubmad_create_rt_work(struct workqueue_struct *rt_wq, e34a52d4eed891 Wen Chen 2025-11-12 142 struct ubmad_msn_mgr *msn_mgr, e34a52d4eed891 Wen Chen 2025-11-12 143 struct ubmad_msg *msg, e34a52d4eed891 Wen Chen 2025-11-12 144 struct ubmad_tjetty *tjetty, e34a52d4eed891 Wen Chen 2025-11-12 145 struct ubmad_jetty_resource *rsrc) e34a52d4eed891 Wen Chen 2025-11-12 146 { e34a52d4eed891 Wen Chen 2025-11-12 147 struct ubmad_rt_work *rt_work; e34a52d4eed891 Wen Chen 2025-11-12 148 e34a52d4eed891 Wen Chen 2025-11-12 149 rt_work = kzalloc(sizeof(struct ubmad_rt_work), e34a52d4eed891 Wen Chen 2025-11-12 150 GFP_KERNEL); // free in ubmad_rt_work_handler() e34a52d4eed891 Wen Chen 2025-11-12 151 if (IS_ERR_OR_NULL(rt_work)) e34a52d4eed891 Wen Chen 2025-11-12 152 return ERR_PTR(-ENOMEM); e34a52d4eed891 Wen Chen 2025-11-12 153 rt_work->msn = msg->msn; e34a52d4eed891 Wen Chen 2025-11-12 154 rt_work->msn_mgr = msn_mgr; e34a52d4eed891 Wen Chen 2025-11-12 155 rt_work->msg = msg; e34a52d4eed891 Wen Chen 2025-11-12 156 rt_work->tjetty = tjetty; e34a52d4eed891 Wen Chen 2025-11-12 157 rt_work->rsrc = rsrc; e34a52d4eed891 Wen Chen 2025-11-12 158 rt_work->rt_wq = rt_wq; e34a52d4eed891 Wen Chen 2025-11-12 159 rt_work->rt_cnt = 0; e34a52d4eed891 Wen Chen 2025-11-12 160 e34a52d4eed891 Wen Chen 2025-11-12 161 INIT_DELAYED_WORK(&rt_work->delay_work, ubmad_rt_work_handler); e34a52d4eed891 Wen Chen 2025-11-12 162 if (queue_delayed_work(rt_wq, &rt_work->delay_work, e34a52d4eed891 Wen Chen 2025-11-12 163 UBMAD_RETRANSMIT_PERIOD) != true) { e34a52d4eed891 Wen Chen 2025-11-12 164 ubcm_log_err("queue rt work failed\n"); e34a52d4eed891 Wen Chen 2025-11-12 165 kfree(rt_work); e34a52d4eed891 Wen Chen 2025-11-12 166 return NULL; e34a52d4eed891 Wen Chen 2025-11-12 167 } e34a52d4eed891 Wen Chen 2025-11-12 168 e34a52d4eed891 Wen Chen 2025-11-12 169 return rt_work; e34a52d4eed891 Wen Chen 2025-11-12 170 } e34a52d4eed891 Wen Chen 2025-11-12 171 :::::: The code at line 141 was first introduced by commit :::::: e34a52d4eed8912f6dfdc7d68152c45f7a071ca8 ubcore: implement ubcore connection management and messaging feature. :::::: TO: Wen Chen <chenwen54(a)huawei.com> :::::: CC: Yongqiang Guo <guoyongqiang12(a)huawei.com> -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[openeuler:OLK-6.6 3534/3534] kernel/dma/contiguous.c:209:13: warning: no previous prototype for function 'is_zhaoxin_kh40000'
by kernel test robot 11 Dec '25

11 Dec '25

Hi leoliu-oc, FYI, the error/warning still remains. tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 423fccda72fc2b78107cc119a1755d968c2c36de commit: 8eaba08b2d72718a40cafe3402ab4f26b0dc62eb [3534/3534] x86/cpu/zhaoxin: Encapsulate access to global variables within functions config: x86_64-randconfig-015-20251211 (https://download.01.org/0day-ci/archive/20251211/202512111016.FVDarhlL-lkp@…) compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512111016.FVDarhlL-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512111016.FVDarhlL-lkp@intel.com/ All warnings (new ones prefixed by >>): In file included from kernel/dma/contiguous.c:48: In file included from include/linux/memblock.h:12: In file included from include/linux/mm.h:2235: include/linux/vmstat.h:508:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion] 508 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS + | ~~~~~~~~~~~~~~~~~~~~~ ^ 509 | item]; | ~~~~ include/linux/vmstat.h:515:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion] 515 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS + | ~~~~~~~~~~~~~~~~~~~~~ ^ 516 | NR_VM_NUMA_EVENT_ITEMS + | ~~~~~~~~~~~~~~~~~~~~~~ include/linux/vmstat.h:522:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion] 522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_" | ~~~~~~~~~~~ ^ ~~~ include/linux/vmstat.h:527:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion] 527 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS + | ~~~~~~~~~~~~~~~~~~~~~ ^ 528 | NR_VM_NUMA_EVENT_ITEMS + | ~~~~~~~~~~~~~~~~~~~~~~ include/linux/vmstat.h:536:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion] 536 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS + | ~~~~~~~~~~~~~~~~~~~~~ ^ 537 | NR_VM_NUMA_EVENT_ITEMS + | ~~~~~~~~~~~~~~~~~~~~~~ >> kernel/dma/contiguous.c:209:13: warning: no previous prototype for function 'is_zhaoxin_kh40000' [-Wmissing-prototypes] 209 | bool __weak is_zhaoxin_kh40000(void) | ^ kernel/dma/contiguous.c:209:1: note: declare 'static' if the function is not intended to be used outside of this translation unit 209 | bool __weak is_zhaoxin_kh40000(void) | ^ | static kernel/dma/contiguous.c:73:26: warning: unused variable 'size_bytes' [-Wunused-const-variable] 73 | static const phys_addr_t size_bytes __initconst = | ^~~~~~~~~~ 7 warnings generated. vim +/is_zhaoxin_kh40000 +209 kernel/dma/contiguous.c 208 > 209 bool __weak is_zhaoxin_kh40000(void) 210 { 211 return false; 212 } 213 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[PATCH openEuler-26.09] just use test patch2pr
by Coopermassaki 11 Dec '25

11 Dec '25

--- README | 1 + 1 file changed, 1 insertion(+) diff --git a/README b/README index 669ac7c32292..e27b37bdb455 100644 --- a/README +++ b/README @@ -16,3 +16,4 @@ several of them using the Restructured Text markup notation. Please read the Documentation/process/changes.rst file, as it contains the requirements for building and running the kernel, and information about the problems which may result by upgrading your kernel. +JUST TEST -- 2.34.1

1 0

[openeuler:OLK-6.6 3529/3529] fs/proc/stat.c:234:18: warning: no previous prototype for function 'bpf_show_all_irqs'
by kernel test robot 11 Dec '25

11 Dec '25

Hi GONG, FYI, the error/warning still remains. tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 423fccda72fc2b78107cc119a1755d968c2c36de commit: 19895b9974c36318281e4e18131a2cfb43543ffd [3529/3529] bpf-rvi: Add stat-related misc kfuncs config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20251211/202512110945.4orBvyVq-lkp@…) compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512110945.4orBvyVq-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512110945.4orBvyVq-lkp@intel.com/ All warnings (new ones prefixed by >>): fs/proc/stat.c:224:17: warning: no previous prototype for function 'bpf_get_idle_time' [-Wmissing-prototypes] 224 | __bpf_kfunc u64 bpf_get_idle_time(struct kernel_cpustat *kcs, int cpu) | ^ fs/proc/stat.c:224:13: note: declare 'static' if the function is not intended to be used outside of this translation unit 224 | __bpf_kfunc u64 bpf_get_idle_time(struct kernel_cpustat *kcs, int cpu) | ^ | static fs/proc/stat.c:229:17: warning: no previous prototype for function 'bpf_get_iowait_time' [-Wmissing-prototypes] 229 | __bpf_kfunc u64 bpf_get_iowait_time(struct kernel_cpustat *kcs, int cpu) | ^ fs/proc/stat.c:229:13: note: declare 'static' if the function is not intended to be used outside of this translation unit 229 | __bpf_kfunc u64 bpf_get_iowait_time(struct kernel_cpustat *kcs, int cpu) | ^ | static >> fs/proc/stat.c:234:18: warning: no previous prototype for function 'bpf_show_all_irqs' [-Wmissing-prototypes] 234 | __bpf_kfunc void bpf_show_all_irqs(struct seq_file *p) | ^ fs/proc/stat.c:234:13: note: declare 'static' if the function is not intended to be used outside of this translation unit 234 | __bpf_kfunc void bpf_show_all_irqs(struct seq_file *p) | ^ | static 3 warnings generated. vim +/bpf_show_all_irqs +234 fs/proc/stat.c 233 > 234 __bpf_kfunc void bpf_show_all_irqs(struct seq_file *p) 235 { 236 show_all_irqs(p); 237 } 238 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[PATCH openEuler-26.09] just use test patch2pr
by Coopermassaki 11 Dec '25

11 Dec '25

--- README | 1 + 1 file changed, 1 insertion(+) diff --git a/README b/README index 669ac7c32292..e27b37bdb455 100644 --- a/README +++ b/README @@ -16,3 +16,4 @@ several of them using the Restructured Text markup notation. Please read the Documentation/process/changes.rst file, as it contains the requirements for building and running the kernel, and information about the problems which may result by upgrading your kernel. +JUST TEST -- 2.34.1

1 0

[openeuler:OLK-6.6 3514/3514] fs/resctrl/monitor.c:51: warning: Cannot understand * @closid_num_dirty_rmid The number of dirty RMID each CLOSID has.
by kernel test robot 11 Dec '25

11 Dec '25

tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: d281438782e3c28a3df71a64513a3312d43dcf01 commit: 13e249bf4944afceae17195b7bb77c767ff61384 [3514/3514] x86/resctrl: Move the filesystem portions of resctrl to live in '/fs/' config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20251211/202512110706.bkOqQiMM-lkp@…) compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512110706.bkOqQiMM-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512110706.bkOqQiMM-lkp@intel.com/ All warnings (new ones prefixed by >>): >> fs/resctrl/monitor.c:51: warning: Cannot understand * @closid_num_dirty_rmid The number of dirty RMID each CLOSID has. on line 51 - I thought it was a doc line vim +51 fs/resctrl/monitor.c 49 50 /** > 51 * @closid_num_dirty_rmid The number of dirty RMID each CLOSID has. 52 * Only allocated when CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID is defined. 53 * Indexed by CLOSID. Protected by rdtgroup_mutex. 54 */ 55 static u32 *closid_num_dirty_rmid; 56 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[openeuler:OLK-6.6 3508/3508] drivers/ub/urma/ubcore/ubcm/ubcm_genl.c:98:20: sparse: sparse: symbol 'g_ubcm_genl_family' was not declared. Should it be static?
by kernel test robot 11 Dec '25

11 Dec '25

tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: d281438782e3c28a3df71a64513a3312d43dcf01 commit: e34a52d4eed8912f6dfdc7d68152c45f7a071ca8 [3508/3508] ubcore: implement ubcore connection management and messaging feature. config: arm64-randconfig-r112-20251210 (https://download.01.org/0day-ci/archive/20251211/202512110717.yxbCknCT-lkp@…) compiler: aarch64-linux-gcc (GCC) 13.4.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512110717.yxbCknCT-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512110717.yxbCknCT-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/ub/urma/ubcore/ubcm/ubcm_genl.c:98:20: sparse: sparse: symbol 'g_ubcm_genl_family' was not declared. Should it be static? vim +/g_ubcm_genl_family +98 drivers/ub/urma/ubcore/ubcm/ubcm_genl.c 97 > 98 struct genl_family g_ubcm_genl_family __ro_after_init = { 99 .hdrsize = 0, 100 .name = UBCM_GENL_FAMILY_NAME, 101 .version = UBCM_GENL_FAMILY_VERSION, 102 .maxattr = UBCM_ATTR_MAX, 103 .policy = g_ubcm_policy, 104 105 .resv_start_op = UBCM_CMD_NUM, 106 107 .netnsok = true, 108 .module = THIS_MODULE, 109 .ops = g_ubcm_genl_ops, 110 .n_ops = ARRAY_SIZE(g_ubcm_genl_ops) 111 }; 112 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[openeuler:OLK-6.6 3529/3529] fs/proc/stat.c:224:17: warning: no previous prototype for function 'bpf_get_idle_time'
by kernel test robot 11 Dec '25

11 Dec '25

Hi GONG, FYI, the error/warning still remains. tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: d281438782e3c28a3df71a64513a3312d43dcf01 commit: 70780f6924c9b58d5a745d4e20e08e9ace28e711 [3529/3529] bpf-rvi: proc: add bpf_get_{idle,iowait}_time kfunc config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20251211/202512110700.3emRQ7Un-lkp@…) compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512110700.3emRQ7Un-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512110700.3emRQ7Un-lkp@intel.com/ All warnings (new ones prefixed by >>): >> fs/proc/stat.c:224:17: warning: no previous prototype for function 'bpf_get_idle_time' [-Wmissing-prototypes] 224 | __bpf_kfunc u64 bpf_get_idle_time(struct kernel_cpustat *kcs, int cpu) | ^ fs/proc/stat.c:224:13: note: declare 'static' if the function is not intended to be used outside of this translation unit 224 | __bpf_kfunc u64 bpf_get_idle_time(struct kernel_cpustat *kcs, int cpu) | ^ | static >> fs/proc/stat.c:229:17: warning: no previous prototype for function 'bpf_get_iowait_time' [-Wmissing-prototypes] 229 | __bpf_kfunc u64 bpf_get_iowait_time(struct kernel_cpustat *kcs, int cpu) | ^ fs/proc/stat.c:229:13: note: declare 'static' if the function is not intended to be used outside of this translation unit 229 | __bpf_kfunc u64 bpf_get_iowait_time(struct kernel_cpustat *kcs, int cpu) | ^ | static 2 warnings generated. vim +/bpf_get_idle_time +224 fs/proc/stat.c 222 223 #ifdef CONFIG_BPF_RVI > 224 __bpf_kfunc u64 bpf_get_idle_time(struct kernel_cpustat *kcs, int cpu) 225 { 226 return get_idle_time(kcs, cpu); 227 } 228 > 229 __bpf_kfunc u64 bpf_get_iowait_time(struct kernel_cpustat *kcs, int cpu) 230 { 231 return get_iowait_time(kcs, cpu); 232 } 233 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[openeuler:OLK-6.6 3508/3508] htmldocs: ./include/drm/drm_atomic.h:246: warning: Function parameter or member 'KABI_RESERVE(1' not described in 'drm_private_state_funcs'
by kernel test robot 11 Dec '25

11 Dec '25

tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: d281438782e3c28a3df71a64513a3312d43dcf01 commit: cfa43356aa8915bedee4920a6c98abdc8a75afa5 [3508/3508] drm: drm_atomic.h: Add kabi_reserve reproduce: (https://download.01.org/0day-ci/archive/20251211/202512110047.nTLxJwrh-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202512110047.nTLxJwrh-lkp@intel.com/ All warnings (new ones prefixed by >>): ./drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:109: warning: Function parameter or member 'top_gain' not described in 'mpcc_blnd_cfg' ./drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:109: warning: Function parameter or member 'bottom_inside_gain' not described in 'mpcc_blnd_cfg' ./drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:109: warning: Function parameter or member 'bottom_outside_gain' not described in 'mpcc_blnd_cfg' Error: Cannot open file ./include/linux/backlight.h Error: Cannot open file ./include/linux/backlight.h >> ./include/drm/drm_atomic.h:246: warning: Function parameter or member 'KABI_RESERVE(1' not described in 'drm_private_state_funcs' >> ./include/drm/drm_atomic.h:347: warning: Function parameter or member 'KABI_RESERVE(1' not described in 'drm_private_state' ./include/drm/drm_connector.h:527: warning: Enum value 'DRM_MODE_COLORIMETRY_COUNT' not described in enum 'drm_colorspace' Error: Cannot open file ./include/linux/hdmi.h Error: Cannot open file ./include/linux/hdmi.h Error: Cannot open file ./include/linux/host1x.h Error: Cannot open file ./include/linux/vga_switcheroo.h vim +246 ./include/drm/drm_atomic.h a4370c777406c28 Ville Syrjälä 2017-07-12 199 b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 200 /** b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 201 * struct drm_private_state_funcs - atomic state functions for private objects b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 202 * b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 203 * These hooks are used by atomic helpers to create, swap and destroy states of b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 204 * private objects. The structure itself is used as a vtable to identify the b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 205 * associated private object type. Each private object type that needs to be b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 206 * added to the atomic states is expected to have an implementation of these 1e55a53a28d3e52 Matt Roper 2019-02-01 207 * hooks and pass a pointer to its drm_private_state_funcs struct to b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 208 * drm_atomic_get_private_obj_state(). b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 209 */ b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 210 struct drm_private_state_funcs { b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 211 /** a4370c777406c28 Ville Syrjälä 2017-07-12 212 * @atomic_duplicate_state: b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 213 * b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 214 * Duplicate the current state of the private object and return it. It b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 215 * is an error to call this before obj->state has been initialized. b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 216 * b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 217 * RETURNS: b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 218 * b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 219 * Duplicated atomic state or NULL when obj->state is not b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 220 * initialized or allocation failed. b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 221 */ a4370c777406c28 Ville Syrjälä 2017-07-12 222 struct drm_private_state *(*atomic_duplicate_state)(struct drm_private_obj *obj); b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 223 b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 224 /** a4370c777406c28 Ville Syrjälä 2017-07-12 225 * @atomic_destroy_state: b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 226 * a4370c777406c28 Ville Syrjälä 2017-07-12 227 * Frees the private object state created with @atomic_duplicate_state. b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 228 */ a4370c777406c28 Ville Syrjälä 2017-07-12 229 void (*atomic_destroy_state)(struct drm_private_obj *obj, a4370c777406c28 Ville Syrjälä 2017-07-12 230 struct drm_private_state *state); 97a1f01b3f2f734 Maxime Ripard 2022-03-28 231 97a1f01b3f2f734 Maxime Ripard 2022-03-28 232 /** 97a1f01b3f2f734 Maxime Ripard 2022-03-28 233 * @atomic_print_state: 97a1f01b3f2f734 Maxime Ripard 2022-03-28 234 * 97a1f01b3f2f734 Maxime Ripard 2022-03-28 235 * If driver subclasses &struct drm_private_state, it should implement 97a1f01b3f2f734 Maxime Ripard 2022-03-28 236 * this optional hook for printing additional driver specific state. 97a1f01b3f2f734 Maxime Ripard 2022-03-28 237 * 97a1f01b3f2f734 Maxime Ripard 2022-03-28 238 * Do not call this directly, use drm_atomic_private_obj_print_state() 97a1f01b3f2f734 Maxime Ripard 2022-03-28 239 * instead. 97a1f01b3f2f734 Maxime Ripard 2022-03-28 240 */ 97a1f01b3f2f734 Maxime Ripard 2022-03-28 241 void (*atomic_print_state)(struct drm_printer *p, 97a1f01b3f2f734 Maxime Ripard 2022-03-28 242 const struct drm_private_state *state); cfa43356aa8915b Lin Yujun 2024-02-04 243 cfa43356aa8915b Lin Yujun 2024-02-04 244 KABI_RESERVE(1) cfa43356aa8915b Lin Yujun 2024-02-04 245 KABI_RESERVE(2) a4370c777406c28 Ville Syrjälä 2017-07-12 @246 }; b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 247 da6c05969785a0f Daniel Vetter 2017-12-14 248 /** da6c05969785a0f Daniel Vetter 2017-12-14 249 * struct drm_private_obj - base struct for driver private atomic object da6c05969785a0f Daniel Vetter 2017-12-14 250 * da6c05969785a0f Daniel Vetter 2017-12-14 251 * A driver private object is initialized by calling da6c05969785a0f Daniel Vetter 2017-12-14 252 * drm_atomic_private_obj_init() and cleaned up by calling da6c05969785a0f Daniel Vetter 2017-12-14 253 * drm_atomic_private_obj_fini(). da6c05969785a0f Daniel Vetter 2017-12-14 254 * da6c05969785a0f Daniel Vetter 2017-12-14 255 * Currently only tracks the state update functions and the opaque driver da6c05969785a0f Daniel Vetter 2017-12-14 256 * private state itself, but in the future might also track which da6c05969785a0f Daniel Vetter 2017-12-14 257 * &drm_modeset_lock is required to duplicate and update this object's state. b962a12050a387e Rob Clark 2018-10-22 258 * b962a12050a387e Rob Clark 2018-10-22 259 * All private objects must be initialized before the DRM device they are b962a12050a387e Rob Clark 2018-10-22 260 * attached to is registered to the DRM subsystem (call to drm_dev_register()) b962a12050a387e Rob Clark 2018-10-22 261 * and should stay around until this DRM device is unregistered (call to b962a12050a387e Rob Clark 2018-10-22 262 * drm_dev_unregister()). In other words, private objects lifetime is tied b962a12050a387e Rob Clark 2018-10-22 263 * to the DRM device lifetime. This implies that: b962a12050a387e Rob Clark 2018-10-22 264 * b962a12050a387e Rob Clark 2018-10-22 265 * 1/ all calls to drm_atomic_private_obj_init() must be done before calling b962a12050a387e Rob Clark 2018-10-22 266 * drm_dev_register() b962a12050a387e Rob Clark 2018-10-22 267 * 2/ all calls to drm_atomic_private_obj_fini() must be done after calling b962a12050a387e Rob Clark 2018-10-22 268 * drm_dev_unregister() 27125e86b797dee Maxime Ripard 2020-12-04 269 * 27125e86b797dee Maxime Ripard 2020-12-04 270 * If that private object is used to store a state shared by multiple 27125e86b797dee Maxime Ripard 2020-12-04 271 * CRTCs, proper care must be taken to ensure that non-blocking commits are 27125e86b797dee Maxime Ripard 2020-12-04 272 * properly ordered to avoid a use-after-free issue. 27125e86b797dee Maxime Ripard 2020-12-04 273 * 27125e86b797dee Maxime Ripard 2020-12-04 274 * Indeed, assuming a sequence of two non-blocking &drm_atomic_commit on two 27125e86b797dee Maxime Ripard 2020-12-04 275 * different &drm_crtc using different &drm_plane and &drm_connector, so with no 27125e86b797dee Maxime Ripard 2020-12-04 276 * resources shared, there's no guarantee on which commit is going to happen 27125e86b797dee Maxime Ripard 2020-12-04 277 * first. However, the second &drm_atomic_commit will consider the first 27125e86b797dee Maxime Ripard 2020-12-04 278 * &drm_private_obj its old state, and will be in charge of freeing it whenever 27125e86b797dee Maxime Ripard 2020-12-04 279 * the second &drm_atomic_commit is done. 27125e86b797dee Maxime Ripard 2020-12-04 280 * 27125e86b797dee Maxime Ripard 2020-12-04 281 * If the first &drm_atomic_commit happens after it, it will consider its 27125e86b797dee Maxime Ripard 2020-12-04 282 * &drm_private_obj the new state and will be likely to access it, resulting in 27125e86b797dee Maxime Ripard 2020-12-04 283 * an access to a freed memory region. Drivers should store (and get a reference 27125e86b797dee Maxime Ripard 2020-12-04 284 * to) the &drm_crtc_commit structure in our private state in 27125e86b797dee Maxime Ripard 2020-12-04 285 * &drm_mode_config_helper_funcs.atomic_commit_setup, and then wait for that 27125e86b797dee Maxime Ripard 2020-12-04 286 * commit to complete as the first step of 27125e86b797dee Maxime Ripard 2020-12-04 287 * &drm_mode_config_helper_funcs.atomic_commit_tail, similar to 27125e86b797dee Maxime Ripard 2020-12-04 288 * drm_atomic_helper_wait_for_dependencies(). da6c05969785a0f Daniel Vetter 2017-12-14 289 */ a4370c777406c28 Ville Syrjälä 2017-07-12 290 struct drm_private_obj { b962a12050a387e Rob Clark 2018-10-22 291 /** b962a12050a387e Rob Clark 2018-10-22 292 * @head: List entry used to attach a private object to a &drm_device b962a12050a387e Rob Clark 2018-10-22 293 * (queued to &drm_mode_config.privobj_list). b962a12050a387e Rob Clark 2018-10-22 294 */ b962a12050a387e Rob Clark 2018-10-22 295 struct list_head head; b962a12050a387e Rob Clark 2018-10-22 296 b962a12050a387e Rob Clark 2018-10-22 297 /** b962a12050a387e Rob Clark 2018-10-22 298 * @lock: Modeset lock to protect the state object. b962a12050a387e Rob Clark 2018-10-22 299 */ b962a12050a387e Rob Clark 2018-10-22 300 struct drm_modeset_lock lock; b962a12050a387e Rob Clark 2018-10-22 301 da6c05969785a0f Daniel Vetter 2017-12-14 302 /** da6c05969785a0f Daniel Vetter 2017-12-14 303 * @state: Current atomic state for this driver private object. da6c05969785a0f Daniel Vetter 2017-12-14 304 */ a4370c777406c28 Ville Syrjälä 2017-07-12 305 struct drm_private_state *state; a4370c777406c28 Ville Syrjälä 2017-07-12 306 da6c05969785a0f Daniel Vetter 2017-12-14 307 /** da6c05969785a0f Daniel Vetter 2017-12-14 308 * @funcs: da6c05969785a0f Daniel Vetter 2017-12-14 309 * da6c05969785a0f Daniel Vetter 2017-12-14 310 * Functions to manipulate the state of this driver private object, see da6c05969785a0f Daniel Vetter 2017-12-14 311 * &drm_private_state_funcs. da6c05969785a0f Daniel Vetter 2017-12-14 312 */ a4370c777406c28 Ville Syrjälä 2017-07-12 313 const struct drm_private_state_funcs *funcs; a4370c777406c28 Ville Syrjälä 2017-07-12 314 }; a4370c777406c28 Ville Syrjälä 2017-07-12 315 b962a12050a387e Rob Clark 2018-10-22 316 /** b962a12050a387e Rob Clark 2018-10-22 317 * drm_for_each_privobj() - private object iterator b962a12050a387e Rob Clark 2018-10-22 318 * b962a12050a387e Rob Clark 2018-10-22 319 * @privobj: pointer to the current private object. Updated after each b962a12050a387e Rob Clark 2018-10-22 320 * iteration b962a12050a387e Rob Clark 2018-10-22 321 * @dev: the DRM device we want get private objects from b962a12050a387e Rob Clark 2018-10-22 322 * b962a12050a387e Rob Clark 2018-10-22 323 * Allows one to iterate over all private objects attached to @dev b962a12050a387e Rob Clark 2018-10-22 324 */ b962a12050a387e Rob Clark 2018-10-22 325 #define drm_for_each_privobj(privobj, dev) \ b962a12050a387e Rob Clark 2018-10-22 326 list_for_each_entry(privobj, &(dev)->mode_config.privobj_list, head) b962a12050a387e Rob Clark 2018-10-22 327 da6c05969785a0f Daniel Vetter 2017-12-14 328 /** da6c05969785a0f Daniel Vetter 2017-12-14 329 * struct drm_private_state - base struct for driver private object state da6c05969785a0f Daniel Vetter 2017-12-14 330 * 97a1f01b3f2f734 Maxime Ripard 2022-03-28 331 * Currently only contains a backpointer to the overall atomic update, 97a1f01b3f2f734 Maxime Ripard 2022-03-28 332 * and the relevant private object but in the future also might hold 97a1f01b3f2f734 Maxime Ripard 2022-03-28 333 * synchronization information similar to e.g. &drm_crtc.commit. da6c05969785a0f Daniel Vetter 2017-12-14 334 */ a4370c777406c28 Ville Syrjälä 2017-07-12 335 struct drm_private_state { 97a1f01b3f2f734 Maxime Ripard 2022-03-28 336 /** 97a1f01b3f2f734 Maxime Ripard 2022-03-28 337 * @state: backpointer to global drm_atomic_state 97a1f01b3f2f734 Maxime Ripard 2022-03-28 338 */ a4370c777406c28 Ville Syrjälä 2017-07-12 339 struct drm_atomic_state *state; 97a1f01b3f2f734 Maxime Ripard 2022-03-28 340 97a1f01b3f2f734 Maxime Ripard 2022-03-28 341 /** 97a1f01b3f2f734 Maxime Ripard 2022-03-28 342 * @obj: backpointer to the private object 97a1f01b3f2f734 Maxime Ripard 2022-03-28 343 */ 97a1f01b3f2f734 Maxime Ripard 2022-03-28 344 struct drm_private_obj *obj; cfa43356aa8915b Lin Yujun 2024-02-04 345 KABI_RESERVE(1) cfa43356aa8915b Lin Yujun 2024-02-04 346 KABI_RESERVE(2) b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 @347 }; b430c27a7de3ccf Pandiyan, Dhinakaran 2017-04-20 348 :::::: The code at line 246 was first introduced by commit :::::: a4370c777406c2810e37fafd166ccddecdb2a60c drm/atomic: Make private objs proper objects :::::: TO: Ville Syrjälä <ville.syrjala(a)linux.intel.com> :::::: CC: Ville Syrjälä <ville.syrjala(a)linux.intel.com> -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0