- Kernel - mailweb.openeuler.org

[PATCH openEuler-1.0-LTS] Revert "fbdev: Fix out-of-bounds issue in sys_fillrect()"
by Gu Bowen 10 Nov '25

10 Nov '25

hulk inclusion category: bugfix bugzilla: https://gitee.com/src-openeuler/kernel/issues/ID5JM1 CVE: NA ------------------ This reverts commit 7389066b79d5dc829e15de2509e43a66bf24e296. This patch caused an issue which a virtual machine could not start, revert it. Fixes: 7389066b79d5 ("fbdev: Fix out-of-bounds issue in sys_fillrect()") Signed-off-by: Gu Bowen <gubowen5(a)huawei.com> --- drivers/video/fbdev/core/fbcon.c | 2 +- drivers/video/fbdev/core/sysfillrect.c | 6 ------ 2 files changed, 1 insertion(+), 7 deletions(-) diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c index e893835c1c25..83a4949e2497 100644 --- a/drivers/video/fbdev/core/fbcon.c +++ b/drivers/video/fbdev/core/fbcon.c @@ -2649,9 +2649,9 @@ static void fbcon_modechanged(struct fb_info *info) return; p = &fb_display[vc->vc_num]; + set_blitting_type(vc, info); if (con_is_visible(vc)) { - set_blitting_type(vc, info); var_to_display(p, &info->var, info); cols = FBCON_SWAP(ops->rotate, info->var.xres, info->var.yres); rows = FBCON_SWAP(ops->rotate, info->var.yres, info->var.xres); diff --git a/drivers/video/fbdev/core/sysfillrect.c b/drivers/video/fbdev/core/sysfillrect.c index 7b4103c3288e..33ee3d34f9d2 100644 --- a/drivers/video/fbdev/core/sysfillrect.c +++ b/drivers/video/fbdev/core/sysfillrect.c @@ -248,7 +248,6 @@ void sys_fillrect(struct fb_info *p, const struct fb_fillrect *rect) u32 bpp = p->var.bits_per_pixel; unsigned long *dst; int dst_idx, left; - long dst_offset; if (p->state != FBINFO_STATE_RUNNING) return; @@ -288,11 +287,6 @@ void sys_fillrect(struct fb_info *p, const struct fb_fillrect *rect) } while (height--) { dst += dst_idx >> (ffs(bits) - 1); - dst_offset = (long)dst - (long)p->screen_base; - if (dst_offset < 0 || dst_offset >= p->fix.smem_len) { - pr_err("dst offset out of bound: dst_offset(%ld)", dst_offset); - return; - } dst_idx &= (bits - 1); fill_op32(p, dst, dst_idx, pat, width*bpp, bits); dst_idx += p->fix.line_length*8; -- 2.43.0

2 1

[PATCH OLK-5.10] slimbus: messaging: Free transaction ID in delayed interrupt scenario
by Xiaomeng Zhang 10 Nov '25

10 Nov '25

From: Visweswara Tanuku <quic_vtanuku(a)quicinc.com> stable inclusion from stable-v5.10.235 commit a32e5198a9134772eb03f7b72a7849094c55bda9 category: bugfix bugzilla: https://gitee.com/src-openeuler/kernel/issues/IBY44F CVE: CVE-2025-21914 Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id… -------------------------------- commit dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a upstream. In case of interrupt delay for any reason, slim_do_transfer() returns timeout error but the transaction ID (TID) is not freed. This results into invalid memory access inside qcom_slim_ngd_rx_msgq_cb() due to invalid TID. Fix the issue by freeing the TID in slim_do_transfer() before returning timeout error to avoid invalid memory access. Call trace: __memcpy_fromio+0x20/0x190 qcom_slim_ngd_rx_msgq_cb+0x130/0x290 [slim_qcom_ngd_ctrl] vchan_complete+0x2a0/0x4a0 tasklet_action_common+0x274/0x700 tasklet_action+0x28/0x3c _stext+0x188/0x620 run_ksoftirqd+0x34/0x74 smpboot_thread_fn+0x1d8/0x464 kthread+0x178/0x238 ret_from_fork+0x10/0x20 Code: aa0003e8 91000429 f100044a 3940002b (3800150b) ---[ end trace 0fe00bec2b975c99 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt. Fixes: afbdcc7c384b ("slimbus: Add messaging APIs to slimbus framework") Cc: stable <stable(a)kernel.org> Signed-off-by: Visweswara Tanuku <quic_vtanuku(a)quicinc.com> Link: https://lore.kernel.org/r/20250124125740.16897-1-quic_vtanuku@quicinc.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Signed-off-by: Wang Hai <wanghai38(a)huawei.com> Signed-off-by: Xiaomeng Zhang <zhangxiaomeng13(a)huawei.com> --- drivers/slimbus/messaging.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/slimbus/messaging.c b/drivers/slimbus/messaging.c index ddf0371ad52b..c1171ec5efeb 100644 --- a/drivers/slimbus/messaging.c +++ b/drivers/slimbus/messaging.c @@ -147,8 +147,9 @@ int slim_do_transfer(struct slim_controller *ctrl, struct slim_msg_txn *txn) } ret = ctrl->xfer_msg(ctrl, txn); - - if (!ret && need_tid && !txn->msg->comp) { + if (ret == -ETIMEDOUT) { + slim_free_txn_tid(ctrl, txn); + } else if (!ret && need_tid && !txn->msg->comp) { unsigned long ms = txn->rl + HZ; timeout = wait_for_completion_timeout(txn->comp, -- 2.34.1

2 1

[PATCH OLK-6.6 v5 0/8] Add xcall 2.0 support
by Jinjie Ruan 10 Nov '25

10 Nov '25

Add xcall 2.0 support, which is compatible with xcall1.0, and can be used to dynamic instruction replacement for hardware xcall. Changes in v5: - Fix build problem. - el0t_64_sync_ventry jump to kernel_ventry to do VMAP_STACK. - Some cleanups. - Merge the three refactor patch. Changes in v4: - Reuse uprobe_write_opcode() instead of use __replace_page() and copy_to_page(). - Handle error for uprobe_write_opcode(). - Support xcall1.0 before 920G. - Change xcall1.0 bitmap to byte array to save check insns. - Use percpu variable to save check insns for xcall1.0. - A little cleanup. Changes in v3: - Add validity checks during xcall registration to prevent out-of-bounds access and null pointer dereferences. - Extract __replace_page() and copy_to_page() from uprobe, to avoid code duplication. - Replace with new compatible refactored code. - Remove unnecessary member, such as old_name. Changes in v2: - Remove duplicates or unnecessary ~300 LOC, such as link_slot, init_task. - Fix kabi. - Some cleanups. Jinjie Ruan (1): xcall2.0: Support xcall1.0 for hardware xcall Liao Chang (6): xcall2.0: Add userspace proc interface xcall2.0: Add xcall module register interface xcall2.0: Add xcall_area xcall2.0: Hajack syscall with dynamic instruciton replace xcall: Refactor the early exception entry for ACTLR.xcall xcall2.0: Add a basic testcase Yuntao Liu (1): xcall2.0: Intruduce xcall2.0 prefetch kernel module arch/arm64/Kconfig.turbo | 13 + arch/arm64/include/asm/exception.h | 4 +- arch/arm64/include/asm/mmu_context.h | 7 - arch/arm64/include/asm/xcall.h | 142 ++++---- arch/arm64/kernel/cpufeature.c | 71 ++-- arch/arm64/kernel/entry-common.c | 28 +- arch/arm64/kernel/entry.S | 86 +---- arch/arm64/kernel/probes/uprobes.c | 6 + arch/arm64/kernel/process.c | 5 + arch/arm64/kernel/syscall.c | 14 + arch/arm64/kernel/xcall/Makefile | 3 +- arch/arm64/kernel/xcall/core.c | 390 +++++++++++++++++++++ arch/arm64/kernel/xcall/entry.S | 133 +++++-- arch/arm64/kernel/xcall/proc.c | 203 +++++++++++ arch/arm64/kernel/xcall/xcall.c | 56 +-- arch/arm64/kvm/sys_regs.c | 1 + drivers/staging/Kconfig | 2 + drivers/staging/Makefile | 1 + drivers/staging/xcall/Kconfig | 19 + drivers/staging/xcall/Makefile | 1 + drivers/staging/xcall/dynamic_xcall_test.c | 97 +++++ drivers/staging/xcall/prefetch.c | 270 ++++++++++++++ fs/proc/proc_xcall.c | 141 ++------ include/linux/mm_types.h | 4 + include/linux/xcall.h | 52 +++ kernel/events/uprobes.c | 23 ++ kernel/fork.c | 3 + mm/mmap.c | 14 +- 28 files changed, 1418 insertions(+), 371 deletions(-) create mode 100644 arch/arm64/kernel/xcall/core.c create mode 100644 arch/arm64/kernel/xcall/proc.c create mode 100644 drivers/staging/xcall/Kconfig create mode 100644 drivers/staging/xcall/Makefile create mode 100644 drivers/staging/xcall/dynamic_xcall_test.c create mode 100644 drivers/staging/xcall/prefetch.c create mode 100644 include/linux/xcall.h -- 2.34.1

2 9

[PATCH OLK-5.10] slimbus: messaging: Free transaction ID in delayed interrupt scenario
by Xiaomeng Zhang 10 Nov '25

10 Nov '25

From: Visweswara Tanuku <quic_vtanuku(a)quicinc.com> stable inclusion from stable-v5.10.235 commit a32e5198a9134772eb03f7b72a7849094c55bda9 category: bugfix bugzilla: 189268 Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id… -------------------------------- commit dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a upstream. In case of interrupt delay for any reason, slim_do_transfer() returns timeout error but the transaction ID (TID) is not freed. This results into invalid memory access inside qcom_slim_ngd_rx_msgq_cb() due to invalid TID. Fix the issue by freeing the TID in slim_do_transfer() before returning timeout error to avoid invalid memory access. Call trace: __memcpy_fromio+0x20/0x190 qcom_slim_ngd_rx_msgq_cb+0x130/0x290 [slim_qcom_ngd_ctrl] vchan_complete+0x2a0/0x4a0 tasklet_action_common+0x274/0x700 tasklet_action+0x28/0x3c _stext+0x188/0x620 run_ksoftirqd+0x34/0x74 smpboot_thread_fn+0x1d8/0x464 kthread+0x178/0x238 ret_from_fork+0x10/0x20 Code: aa0003e8 91000429 f100044a 3940002b (3800150b) ---[ end trace 0fe00bec2b975c99 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt. Fixes: afbdcc7c384b ("slimbus: Add messaging APIs to slimbus framework") Cc: stable <stable(a)kernel.org> Signed-off-by: Visweswara Tanuku <quic_vtanuku(a)quicinc.com> Link: https://lore.kernel.org/r/20250124125740.16897-1-quic_vtanuku@quicinc.com Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Signed-off-by: Wang Hai <wanghai38(a)huawei.com> Signed-off-by: Xiaomeng Zhang <zhangxiaomeng13(a)huawei.com> --- drivers/slimbus/messaging.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/slimbus/messaging.c b/drivers/slimbus/messaging.c index ddf0371ad52b..c1171ec5efeb 100644 --- a/drivers/slimbus/messaging.c +++ b/drivers/slimbus/messaging.c @@ -147,8 +147,9 @@ int slim_do_transfer(struct slim_controller *ctrl, struct slim_msg_txn *txn) } ret = ctrl->xfer_msg(ctrl, txn); - - if (!ret && need_tid && !txn->msg->comp) { + if (ret == -ETIMEDOUT) { + slim_free_txn_tid(ctrl, txn); + } else if (!ret && need_tid && !txn->msg->comp) { unsigned long ms = txn->rl + HZ; timeout = wait_for_completion_timeout(txn->comp, -- 2.34.1

2 1

[PATCH OLK-5.10] ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans
by Xiaomeng Zhang 10 Nov '25

10 Nov '25

From: Yajun Deng <yajun.deng(a)linux.dev> stable inclusion from stable-v5.10.236 commit de203da734fae00e75be50220ba5391e7beecdf9 category: bugfix bugzilla: https://gitee.com/src-openeuler/kernel/issues/IC1QP4 CVE: CVE-2023-53034 Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id… -------------------------------- [ Upstream commit de203da734fae00e75be50220ba5391e7beecdf9 ] There is a kernel API ntb_mw_clear_trans() would pass 0 to both addr and size. This would make xlate_pos negative. [ 23.734156] switchtec switchtec0: MW 0: part 0 addr 0x0000000000000000 size 0x0000000000000000 [ 23.734158] ================================================================================ [ 23.734172] UBSAN: shift-out-of-bounds in drivers/ntb/hw/mscc/ntb_hw_switchtec.c:293:7 [ 23.734418] shift exponent -1 is negative Ensuring xlate_pos is a positive or zero before BIT. Fixes: 1e2fd202f859 ("ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()") Signed-off-by: Yajun Deng <yajun.deng(a)linux.dev> Reviewed-by: Logan Gunthorpe <logang(a)deltatee.com> Signed-off-by: Jon Mason <jdmason(a)kudzu.us> Signed-off-by: Sasha Levin <sashal(a)kernel.org> Signed-off-by: Xiaomeng Zhang <zhangxiaomeng13(a)huawei.com> --- drivers/ntb/hw/mscc/ntb_hw_switchtec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/ntb/hw/mscc/ntb_hw_switchtec.c b/drivers/ntb/hw/mscc/ntb_hw_switchtec.c index ad09946100b5..c5c1963c699d 100644 --- a/drivers/ntb/hw/mscc/ntb_hw_switchtec.c +++ b/drivers/ntb/hw/mscc/ntb_hw_switchtec.c @@ -288,7 +288,7 @@ static int switchtec_ntb_mw_set_trans(struct ntb_dev *ntb, int pidx, int widx, if (size != 0 && xlate_pos < 12) return -EINVAL; - if (!IS_ALIGNED(addr, BIT_ULL(xlate_pos))) { + if (xlate_pos >= 0 && !IS_ALIGNED(addr, BIT_ULL(xlate_pos))) { /* * In certain circumstances we can get a buffer that is * not aligned to its size. (Most of the time -- 2.34.1

2 1

[PATCH OLK-5.10 0/3] wakeup kswapd during node_reclaim
by Wupeng Ma 10 Nov '25

10 Nov '25

Wakeup kswapd during node_reclaim and add new bits for zone recalim to enable this kind of behavior. Wupeng Ma (3): arm64/numa: Make node reclaim distance adjustment always available mm: vmscan: wakeup kswapd during node_reclaim mm: node_reclaim: add wakeup kswapd mode Documentation/admin-guide/sysctl/vm.rst | 1 + arch/arm64/mm/numa.c | 40 ++++++++++++------------- mm/internal.h | 5 ++-- mm/page_alloc.c | 3 +- mm/vmscan.c | 8 ++++- 5 files changed, 33 insertions(+), 24 deletions(-) -- 2.43.0

2 4

[PATCH OLK-6.6] mm: introduce memalloc_flags_{save,restore}
by Long Li 10 Nov '25

10 Nov '25

From: Kent Overstreet <kent.overstreet(a)linux.dev> mainline inclusion from mainline-v6.8-rc6 commit 3f6d5e6a468d02676244b868b210433831846127 category: bugfix bugzilla: https://gitee.com/openeuler/kernel/issues/ID55JW Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… -------------------------------- Our proliferation of memalloc_*_{save,restore} APIs is getting a bit silly, this adds a generic version and converts the existing save/restore functions to wrappers. Signed-off-by: Kent Overstreet <kent.overstreet(a)linux.dev> Cc: Vlastimil Babka <vbabka(a)suse.cz> Cc: Matthew Wilcox <willy(a)infradead.org> Cc: Michal Hocko <mhocko(a)kernel.org> Cc: Darrick J. Wong <djwong(a)kernel.org> Cc: linux-mm(a)kvack.org Acked-by: Vlastimil Babka <vbabka(a)suse.cz> Signed-off-by: Long Li <leo.lilong(a)huawei.com> --- include/linux/sched/mm.h | 43 ++++++++++++++++++++++++---------------- 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/include/linux/sched/mm.h b/include/linux/sched/mm.h index 9a19f1b42f64..f00d7ecc2adf 100644 --- a/include/linux/sched/mm.h +++ b/include/linux/sched/mm.h @@ -306,6 +306,24 @@ static inline void might_alloc(gfp_t gfp_mask) might_sleep_if(gfpflags_allow_blocking(gfp_mask)); } +/** + * memalloc_flags_save - Add a PF_* flag to current->flags, save old value + * + * This allows PF_* flags to be conveniently added, irrespective of current + * value, and then the old version restored with memalloc_flags_restore(). + */ +static inline unsigned memalloc_flags_save(unsigned flags) +{ + unsigned oldflags = ~current->flags & flags; + current->flags |= flags; + return oldflags; +} + +static inline void memalloc_flags_restore(unsigned flags) +{ + current->flags &= ~flags; +} + /** * memalloc_noio_save - Marks implicit GFP_NOIO allocation scope. * @@ -319,9 +337,7 @@ static inline void might_alloc(gfp_t gfp_mask) */ static inline unsigned int memalloc_noio_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC_NOIO; - current->flags |= PF_MEMALLOC_NOIO; - return flags; + return memalloc_flags_save(PF_MEMALLOC_NOIO); } /** @@ -334,7 +350,7 @@ static inline unsigned int memalloc_noio_save(void) */ static inline void memalloc_noio_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC_NOIO) | flags; + memalloc_flags_restore(flags); } /** @@ -350,9 +366,7 @@ static inline void memalloc_noio_restore(unsigned int flags) */ static inline unsigned int memalloc_nofs_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC_NOFS; - current->flags |= PF_MEMALLOC_NOFS; - return flags; + return memalloc_flags_save(PF_MEMALLOC_NOFS); } /** @@ -365,32 +379,27 @@ static inline unsigned int memalloc_nofs_save(void) */ static inline void memalloc_nofs_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC_NOFS) | flags; + memalloc_flags_restore(flags); } static inline unsigned int memalloc_noreclaim_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC; - current->flags |= PF_MEMALLOC; - return flags; + return memalloc_flags_save(PF_MEMALLOC); } static inline void memalloc_noreclaim_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC) | flags; + memalloc_flags_restore(flags); } static inline unsigned int memalloc_pin_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC_PIN; - - current->flags |= PF_MEMALLOC_PIN; - return flags; + return memalloc_flags_save(PF_MEMALLOC_PIN); } static inline void memalloc_pin_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC_PIN) | flags; + memalloc_flags_restore(flags); } #ifdef CONFIG_MEMCG -- 2.39.2

2 1

[PATCH OLK-5.10] mm: introduce memalloc_flags_{save,restore}
by Long Li 10 Nov '25

10 Nov '25

From: Kent Overstreet <kent.overstreet(a)linux.dev> mainline inclusion from mainline-v6.8-rc6 commit 3f6d5e6a468d02676244b868b210433831846127 category: bugfix bugzilla: https://gitee.com/openeuler/kernel/issues/ID55JW Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… -------------------------------- Our proliferation of memalloc_*_{save,restore} APIs is getting a bit silly, this adds a generic version and converts the existing save/restore functions to wrappers. Signed-off-by: Kent Overstreet <kent.overstreet(a)linux.dev> Cc: Vlastimil Babka <vbabka(a)suse.cz> Cc: Matthew Wilcox <willy(a)infradead.org> Cc: Michal Hocko <mhocko(a)kernel.org> Cc: Darrick J. Wong <djwong(a)kernel.org> Cc: linux-mm(a)kvack.org Acked-by: Vlastimil Babka <vbabka(a)suse.cz> Fixes: 853af6c55a18 ("[Backport] xfs: don't use current->journal_info") Conflicts: include/linux/sched/mm.h [Not merage commit 1a08ae36cf8b ("mm cma: rename PF_MEMALLOC_NOCMA to PF_MEMALLOC_PIN")] Signed-off-by: Long Li <leo.lilong(a)huawei.com> --- include/linux/sched/mm.h | 43 ++++++++++++++++++++++++---------------- 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/include/linux/sched/mm.h b/include/linux/sched/mm.h index f58a2730a130..44ec7dc8cc71 100644 --- a/include/linux/sched/mm.h +++ b/include/linux/sched/mm.h @@ -190,6 +190,24 @@ static inline void fs_reclaim_acquire(gfp_t gfp_mask) { } static inline void fs_reclaim_release(gfp_t gfp_mask) { } #endif +/** + * memalloc_flags_save - Add a PF_* flag to current->flags, save old value + * + * This allows PF_* flags to be conveniently added, irrespective of current + * value, and then the old version restored with memalloc_flags_restore(). + */ +static inline unsigned memalloc_flags_save(unsigned flags) +{ + unsigned oldflags = ~current->flags & flags; + current->flags |= flags; + return oldflags; +} + +static inline void memalloc_flags_restore(unsigned flags) +{ + current->flags &= ~flags; +} + /** * memalloc_noio_save - Marks implicit GFP_NOIO allocation scope. * @@ -203,9 +221,7 @@ static inline void fs_reclaim_release(gfp_t gfp_mask) { } */ static inline unsigned int memalloc_noio_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC_NOIO; - current->flags |= PF_MEMALLOC_NOIO; - return flags; + return memalloc_flags_save(PF_MEMALLOC_NOIO); } /** @@ -218,7 +234,7 @@ static inline unsigned int memalloc_noio_save(void) */ static inline void memalloc_noio_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC_NOIO) | flags; + memalloc_flags_restore(flags); } /** @@ -234,9 +250,7 @@ static inline void memalloc_noio_restore(unsigned int flags) */ static inline unsigned int memalloc_nofs_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC_NOFS; - current->flags |= PF_MEMALLOC_NOFS; - return flags; + return memalloc_flags_save(PF_MEMALLOC_NOFS); } /** @@ -249,33 +263,28 @@ static inline unsigned int memalloc_nofs_save(void) */ static inline void memalloc_nofs_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC_NOFS) | flags; + memalloc_flags_restore(flags); } static inline unsigned int memalloc_noreclaim_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC; - current->flags |= PF_MEMALLOC; - return flags; + return memalloc_flags_save(PF_MEMALLOC); } static inline void memalloc_noreclaim_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC) | flags; + memalloc_flags_restore(flags); } #ifdef CONFIG_CMA static inline unsigned int memalloc_nocma_save(void) { - unsigned int flags = current->flags & PF_MEMALLOC_NOCMA; - - current->flags |= PF_MEMALLOC_NOCMA; - return flags; + return memalloc_flags_save(PF_MEMALLOC_NOCMA); } static inline void memalloc_nocma_restore(unsigned int flags) { - current->flags = (current->flags & ~PF_MEMALLOC_NOCMA) | flags; + memalloc_flags_restore(flags); } #else static inline unsigned int memalloc_nocma_save(void) -- 2.39.2

2 1

[openeuler:OLK-6.6 3124/3124] drivers/ub/ubfi/ummu.c:24:1: error: expected member name or ';' after declaration specifiers
by kernel test robot 09 Nov '25

09 Nov '25

tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 66984acf4b16f28a2cc0d5d6186b4b6bbfd92e26 commit: 010c6364261c263f01d3d7861a955f3b1c2c9156 [3124/3124] ub: ubfi: Parsing ummu node in the ubrt table config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20251109/202511092145.WGq6xLTY-lkp@…) compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251109/202511092145.WGq6xLTY-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/202511092145.WGq6xLTY-lkp@intel.com/ All error/warnings (new ones prefixed by >>): >> drivers/ub/ubfi/ummu.c:24:1: error: expected member name or ';' after declaration specifiers 24 | }; | ^ >> drivers/ub/ubfi/ummu.c:24:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int] 23 | u8 node_data[]; __counted_by(count) | int 24 | }; | ^ >> drivers/ub/ubfi/ummu.c:23:18: error: 'counted_by' only applies to pointers or C99 flexible array members 23 | u8 node_data[]; __counted_by(count) | ^~~~~~~~~~~~~~~~~~~ include/linux/compiler_types.h:320:32: note: expanded from macro '__counted_by' 320 | # define __counted_by(member) __attribute__((__counted_by__(member))) | ^~~~~~~~~~~~~ >> drivers/ub/ubfi/ummu.c:23:37: warning: expected ';' at end of declaration list 23 | u8 node_data[]; __counted_by(count) | ^ | ; >> drivers/ub/ubfi/ummu.c:23:5: error: flexible array member 'node_data' with type 'u8[]' (aka 'unsigned char[]') is not at the end of struct 23 | u8 node_data[]; __counted_by(count) | ^ drivers/ub/ubfi/ummu.c:23:18: note: next field declaration is here 23 | u8 node_data[]; __counted_by(count) | ^ include/linux/compiler_types.h:320:32: note: expanded from macro '__counted_by' 320 | # define __counted_by(member) __attribute__((__counted_by__(member))) | ^ 1 warning and 4 errors generated. -- >> drivers/ub/ubfi/resv_mem.c:33:1: error: expected member name or ';' after declaration specifiers 33 | }; | ^ >> drivers/ub/ubfi/resv_mem.c:33:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int] 32 | u8 ranges[]; __counted_by(count) | int 33 | }; | ^ >> drivers/ub/ubfi/resv_mem.c:32:15: error: 'counted_by' only applies to pointers or C99 flexible array members 32 | u8 ranges[]; __counted_by(count) | ^~~~~~~~~~~~~~~~~~~ include/linux/compiler_types.h:320:32: note: expanded from macro '__counted_by' 320 | # define __counted_by(member) __attribute__((__counted_by__(member))) | ^~~~~~~~~~~~~ >> drivers/ub/ubfi/resv_mem.c:32:34: warning: expected ';' at end of declaration list 32 | u8 ranges[]; __counted_by(count) | ^ | ; >> drivers/ub/ubfi/resv_mem.c:32:5: error: flexible array member 'ranges' with type 'u8[]' (aka 'unsigned char[]') is not at the end of struct 32 | u8 ranges[]; __counted_by(count) | ^ drivers/ub/ubfi/resv_mem.c:32:15: note: next field declaration is here 32 | u8 ranges[]; __counted_by(count) | ^ include/linux/compiler_types.h:320:32: note: expanded from macro '__counted_by' 320 | # define __counted_by(member) __attribute__((__counted_by__(member))) | ^ 1 warning and 4 errors generated. vim +24 drivers/ub/ubfi/ummu.c 18 19 struct ummu_sub_table { 20 struct ub_table_header header; 21 u16 count; 22 u8 reserved[6]; > 23 u8 node_data[]; __counted_by(count) > 24 }; 25 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0

[openeuler:OLK-6.6 3124/3124] drivers/ub/ubase/ubase_pmem.c:239:4: error: a randomized struct can only be initialized with a designated initializer
by kernel test robot 09 Nov '25

09 Nov '25

tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 66984acf4b16f28a2cc0d5d6186b4b6bbfd92e26 commit: da7d25293a382c506d3d46f06aff4074d881f24f [3124/3124] ub: ubase: support pre-alloc 2M pages. config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20251109/202511091319.N8VHQUDq-lkp@…) compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251109/202511091319.N8VHQUDq-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/202511091319.N8VHQUDq-lkp@intel.com/ All error/warnings (new ones prefixed by >>): >> drivers/ub/ubase/ubase_hw.c:430:5: warning: no previous prototype for function 'ubase_cmd_ctx_buf_alloc' [-Wmissing-prototypes] 430 | int ubase_cmd_ctx_buf_alloc(struct ubase_dev *udev, | ^ drivers/ub/ubase/ubase_hw.c:430:1: note: declare 'static' if the function is not intended to be used outside of this translation unit 430 | int ubase_cmd_ctx_buf_alloc(struct ubase_dev *udev, | ^ | static 1 warning generated. -- >> drivers/ub/ubase/ubase_pmem.c:239:4: error: a randomized struct can only be initialized with a designated initializer 239 | { ubase_init_comm_pmem_ctx, ubase_uninit_comm_pmem_ctx }, | ^ drivers/ub/ubase/ubase_pmem.c:240:4: error: a randomized struct can only be initialized with a designated initializer 240 | { ubase_init_udma_pmem_ctx, ubase_uninit_udma_pmem_ctx }, | ^ drivers/ub/ubase/ubase_pmem.c:241:4: error: a randomized struct can only be initialized with a designated initializer 241 | { ubase_alloc_comm_pmem, ubase_free_comm_pmem }, | ^ drivers/ub/ubase/ubase_pmem.c:242:4: error: a randomized struct can only be initialized with a designated initializer 242 | { ubase_alloc_udma_pmem, ubase_free_udma_pmem }, | ^ drivers/ub/ubase/ubase_pmem.c:243:4: error: a randomized struct can only be initialized with a designated initializer 243 | { ubase_map_comm_pmem, ubase_unmap_comm_pmem }, | ^ drivers/ub/ubase/ubase_pmem.c:244:4: error: a randomized struct can only be initialized with a designated initializer 244 | { ubase_map_udma_pmem, ubase_unmap_udma_pmem }, | ^ >> drivers/ub/ubase/ubase_pmem.c:251:18: error: invalid application of 'sizeof' to an incomplete type 'const struct ubase_pmem_init_func[]' 251 | for (i = 0; i < ARRAY_SIZE(ubase_pmem_init_map); i++) { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ include/linux/kernel.h:57:32: note: expanded from macro 'ARRAY_SIZE' 57 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr)) | ^~~~~ drivers/ub/ubase/ubase_pmem.c:315:11: error: invalid application of 'sizeof' to an incomplete type 'const struct ubase_pmem_init_func[]' 315 | for (i = ARRAY_SIZE(ubase_pmem_init_map) - 1; i >= 0; i--) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ include/linux/kernel.h:57:32: note: expanded from macro 'ARRAY_SIZE' 57 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr)) | ^~~~~ 8 errors generated. vim +239 drivers/ub/ubase/ubase_pmem.c 234 235 static const struct ubase_pmem_init_func { 236 int (*init)(struct ubase_dev *udev); 237 void (*uninit)(struct ubase_dev *udev); 238 } ubase_pmem_init_map[] = { > 239 { ubase_init_comm_pmem_ctx, ubase_uninit_comm_pmem_ctx }, 240 { ubase_init_udma_pmem_ctx, ubase_uninit_udma_pmem_ctx }, 241 { ubase_alloc_comm_pmem, ubase_free_comm_pmem }, > 242 { ubase_alloc_udma_pmem, ubase_free_udma_pmem }, 243 { ubase_map_comm_pmem, ubase_unmap_comm_pmem }, 244 { ubase_map_udma_pmem, ubase_unmap_udma_pmem }, 245 }; 246 247 static int __ubase_prealloc_mem_init(struct ubase_dev *udev) 248 { 249 int i; 250 > 251 for (i = 0; i < ARRAY_SIZE(ubase_pmem_init_map); i++) { 252 if (ubase_pmem_init_map[i].init(udev)) 253 goto init_fail; 254 } 255 256 return 0; 257 258 init_fail: 259 for (i -= 1; i >= 0; i--) 260 ubase_pmem_init_map[i].uninit(udev); 261 262 return -ENOMEM; 263 } 264 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 0