tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: 3841d75a6dcd12d108aaf56560b99431d18169e4
commit: 4a280fac30d27ae2aff096f9f99aa12d50f83426 [18183/23799] ascend: share_pool: support share pool features for ascend platform
config: arm64-randconfig-003-20240928 (https://download.01.org/0day-ci/archive/20240928/202409280759.ueQXB2WQ-lkp@…)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240928/202409280759.ueQXB2WQ-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/202409280759.ueQXB2WQ-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
mm/share_pool.c: In function 'sp_hugetlb_entry':
>> mm/share_pool.c:1542:21: error: implicit declaration of function 'huge_ptep_get' [-Werror=implicit-function-declaration]
1542 | pte_t pte = huge_ptep_get(ptep);
| ^~~~~~~~~~~~~
>> mm/share_pool.c:1542:21: error: invalid initializer
mm/share_pool.c: In function 'sp_alloc_pages':
>> mm/share_pool.c:2263:24: error: implicit declaration of function 'hugetlb_alloc_hugepage'; did you mean 'vmalloc_hugepage'? [-Werror=implicit-function-declaration]
2263 | return hugetlb_alloc_hugepage(NUMA_NO_NODE, HUGETLB_ALLOC_NONE);
| ^~~~~~~~~~~~~~~~~~~~~~
| vmalloc_hugepage
>> mm/share_pool.c:2263:61: error: 'HUGETLB_ALLOC_NONE' undeclared (first use in this function); did you mean 'HUGETLB_ANON_FILE'?
2263 | return hugetlb_alloc_hugepage(NUMA_NO_NODE, HUGETLB_ALLOC_NONE);
| ^~~~~~~~~~~~~~~~~~
| HUGETLB_ANON_FILE
mm/share_pool.c:2263:61: note: each undeclared identifier is reported only once for each function it appears in
mm/share_pool.c:2266:1: warning: control reaches end of non-void function [-Wreturn-type]
2266 | }
| ^
mm/share_pool.c: At top level:
>> mm/share_pool.c:2235:12: warning: 'spa_stat_show' defined but not used [-Wunused-function]
2235 | static int spa_stat_show(struct seq_file *seq, void *offset)
| ^~~~~~~~~~~~~
>> mm/share_pool.c:2121:12: warning: 'proc_stat_show' defined but not used [-Wunused-function]
2121 | static int proc_stat_show(struct seq_file *seq, void *offset)
| ^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/huge_ptep_get +1542 mm/share_pool.c
1537
1538 static int sp_hugetlb_entry(pte_t *ptep, unsigned long hmask,
1539 unsigned long addr, unsigned long next,
1540 struct mm_walk *walk)
1541 {
> 1542 pte_t pte = huge_ptep_get(ptep);
1543 struct page *page = pte_page(pte);
1544 struct sp_walk_data *sp_walk_data;
1545
1546 if (unlikely(!pte_present(pte))) {
1547 if (printk_ratelimit())
1548 pr_err("share pool: the page of addr %pK unexpectedly not in RAM\n", (void *)addr);
1549 return -EFAULT;
1550 }
1551
1552 sp_walk_data = walk->private;
1553 get_page(page);
1554 sp_walk_data->pages[sp_walk_data->page_count++] = page;
1555 return 0;
1556 }
1557
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Hi Weilong,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: c9fe32fed709da98069e8215f6ecf39ea63f5355
commit: b498d9f1bacd40d583c0970cab02ad522127a7e7 [1683/14216] arm64/ascend: Add new enable_oom_killer interface for oom contrl
config: arm64-randconfig-002-20240928 (https://download.01.org/0day-ci/archive/20240928/202409280536.wLGz5QQ3-lkp@…)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240928/202409280536.wLGz5QQ3-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/202409280536.wLGz5QQ3-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/memcontrol.c:3147:6: warning: no previous prototype for 'hisi_oom_recover' [-Wmissing-prototypes]
3147 | void hisi_oom_recover(struct obj_cgroup *objcg)
| ^~~~~~~~~~~~~~~~
vim +/hisi_oom_recover +3147 mm/memcontrol.c
3145
3146 #ifdef CONFIG_ASCEND_OOM
> 3147 void hisi_oom_recover(struct obj_cgroup *objcg)
3148 {
3149 struct mem_cgroup *memcg;
3150
3151 memcg = get_mem_cgroup_from_objcg(objcg);
3152 if (!mem_cgroup_is_root(memcg))
3153 memcg_oom_recover(memcg);
3154 css_put(&memcg->css);
3155 }
3156 #else
3157 static inline void hisi_oom_recover(struct obj_cgroup *objcg) { }
3158 #endif
3159
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Hi Hongbo,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: bef6f06e039b8929481350d15d6d8c3ba81c6fd2
commit: 923efc4dc37c1a7cc91f0dd5dbdc87e0943ad1ae [2613/30000] tty: fix possible deadlock in console_unlock
config: arm64-randconfig-002-20240928 (https://download.01.org/0day-ci/archive/20240928/202409280444.fQT7iGoe-lkp@…)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240928/202409280444.fQT7iGoe-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/202409280444.fQT7iGoe-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/tty/tty_buffer.c: In function 'tty_buffer_alloc':
drivers/tty/tty_buffer.c:175:9: error: implicit declaration of function 'printk_safe_enter'; did you mean 'printk_nmi_enter'? [-Werror=implicit-function-declaration]
175 | printk_safe_enter();
| ^~~~~~~~~~~~~~~~~
| printk_nmi_enter
>> drivers/tty/tty_buffer.c:177:9: error: implicit declaration of function 'printk_safe_exit'; did you mean 'printk_nmi_exit'? [-Werror=implicit-function-declaration]
177 | printk_safe_exit();
| ^~~~~~~~~~~~~~~~
| printk_nmi_exit
cc1: some warnings being treated as errors
vim +177 drivers/tty/tty_buffer.c
142
143 /**
144 * tty_buffer_alloc - allocate a tty buffer
145 * @port: tty port
146 * @size: desired size (characters)
147 *
148 * Allocate a new tty buffer to hold the desired number of characters.
149 * We round our buffers off in 256 character chunks to get better
150 * allocation behaviour.
151 * Return NULL if out of memory or the allocation would exceed the
152 * per device queue
153 */
154
155 static struct tty_buffer *tty_buffer_alloc(struct tty_port *port, size_t size)
156 {
157 struct llist_node *free;
158 struct tty_buffer *p;
159
160 /* Round the buffer size out */
161 size = __ALIGN_MASK(size, TTYB_ALIGN_MASK);
162
163 if (size <= MIN_TTYB_SIZE) {
164 free = llist_del_first(&port->buf.free);
165 if (free) {
166 p = llist_entry(free, struct tty_buffer, free);
167 goto found;
168 }
169 }
170
171 /* Should possibly check if this fails for the largest buffer we
172 have queued and recycle that ? */
173 if (atomic_read(&port->buf.mem_used) > port->buf.mem_limit)
174 return NULL;
175 printk_safe_enter();
176 p = kmalloc(sizeof(struct tty_buffer) + 2 * size, GFP_ATOMIC);
> 177 printk_safe_exit();
178 if (p == NULL)
179 return NULL;
180
181 found:
182 tty_buffer_reset(p, size);
183 atomic_add(size, &port->buf.mem_used);
184 return p;
185 }
186
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Hi Yu'an,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: 3841d75a6dcd12d108aaf56560b99431d18169e4
commit: 73d33f5c59dc3824444baca6a458427f4de3d8fa [13192/23799] qm: Move all the same logic functions of hisilicon crypto to qm
config: arm64-randconfig-002-20240928 (https://download.01.org/0day-ci/archive/20240928/202409280341.XkIGO1R8-lkp@…)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240928/202409280341.XkIGO1R8-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/202409280341.XkIGO1R8-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/crypto/hisilicon/qm.c:2726: warning: Excess function parameter 'ce' description in 'qm_hw_error_init'
>> drivers/crypto/hisilicon/qm.c:2726: warning: Excess function parameter 'nfe' description in 'qm_hw_error_init'
>> drivers/crypto/hisilicon/qm.c:2726: warning: Excess function parameter 'fe' description in 'qm_hw_error_init'
>> drivers/crypto/hisilicon/qm.c:2726: warning: Excess function parameter 'msi' description in 'qm_hw_error_init'
vim +2726 drivers/crypto/hisilicon/qm.c
ae67d23af736c7 xuzaibo 2019-04-21 2706
ae67d23af736c7 xuzaibo 2019-04-21 2707 /**
73d33f5c59dc38 Yu'an Wang 2020-04-16 2708 * qm_hw_error_init() - Configure qm hardware error report method.
ae67d23af736c7 xuzaibo 2019-04-21 2709 * @qm: The qm which we want to configure.
ae67d23af736c7 xuzaibo 2019-04-21 2710 * @ce: Correctable error configure.
ae67d23af736c7 xuzaibo 2019-04-21 2711 * @nfe: Non-fatal error configure.
ae67d23af736c7 xuzaibo 2019-04-21 2712 * @fe: Fatal error configure.
ae67d23af736c7 xuzaibo 2019-04-21 2713 * @msi: Error reported by message signal interrupt.
ae67d23af736c7 xuzaibo 2019-04-21 2714 *
ae67d23af736c7 xuzaibo 2019-04-21 2715 * Hardware errors of qm can be reported either by RAS interrupts which will
ae67d23af736c7 xuzaibo 2019-04-21 2716 * be handled by UEFI and then PCIe AER or by device MSI. User can configure
ae67d23af736c7 xuzaibo 2019-04-21 2717 * each error to use either of above two methods. For RAS interrupts, we can
ae67d23af736c7 xuzaibo 2019-04-21 2718 * configure an error as one of correctable error, non-fatal error or
ae67d23af736c7 xuzaibo 2019-04-21 2719 * fatal error.
ae67d23af736c7 xuzaibo 2019-04-21 2720 *
ae67d23af736c7 xuzaibo 2019-04-21 2721 * Bits indicating errors can be configured to ce, nfe, fe and msi to enable
ae67d23af736c7 xuzaibo 2019-04-21 2722 * related report methods. Error report will be masked if related error bit
ae67d23af736c7 xuzaibo 2019-04-21 2723 * does not configure.
ae67d23af736c7 xuzaibo 2019-04-21 2724 */
73d33f5c59dc38 Yu'an Wang 2020-04-16 2725 static void qm_hw_error_init(struct hisi_qm *qm)
ae67d23af736c7 xuzaibo 2019-04-21 @2726 {
73d33f5c59dc38 Yu'an Wang 2020-04-16 2727 u32 nfe = qm->err_ini.err_info.nfe;
73d33f5c59dc38 Yu'an Wang 2020-04-16 2728 u32 msi = qm->err_ini.err_info.msi;
73d33f5c59dc38 Yu'an Wang 2020-04-16 2729 u32 ce = qm->err_ini.err_info.ce;
73d33f5c59dc38 Yu'an Wang 2020-04-16 2730 u32 fe = qm->err_ini.err_info.fe;
73d33f5c59dc38 Yu'an Wang 2020-04-16 2731
ae67d23af736c7 xuzaibo 2019-04-21 2732 if (!qm->ops->hw_error_init) {
ae67d23af736c7 xuzaibo 2019-04-21 2733 dev_err(&qm->pdev->dev,
ae67d23af736c7 xuzaibo 2019-04-21 2734 "QM version %d doesn't support hw error handling!\n",
ae67d23af736c7 xuzaibo 2019-04-21 2735 qm->ver);
ae67d23af736c7 xuzaibo 2019-04-21 2736 return;
ae67d23af736c7 xuzaibo 2019-04-21 2737 }
ae67d23af736c7 xuzaibo 2019-04-21 2738
efe221f95003ac Zhou Wang 2019-07-11 2739 qm->ops->hw_error_init(qm, ce, nfe, fe, msi);
ae67d23af736c7 xuzaibo 2019-04-21 2740 }
ae67d23af736c7 xuzaibo 2019-04-21 2741
:::::: The code at line 2726 was first introduced by commit
:::::: ae67d23af736c75f90795297fddb86dc97e7b3c7 arm64: Add hisilicon Crypto drivers qm/hpre/zip and code format
:::::: TO: xuzaibo <xuzaibo(a)huawei.com>
:::::: CC: Xie XiuQi <xiexiuqi(a)huawei.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki