[ANNOUNCE] Release v4.19.325-cip123

[ANNOUNCE] Release v4.19.325-cip123

[Ulrich Hecht]

Hi,

the CIP kernel team has released Linux kernel v4.19.325-cip123. The linux-4.19.y-cip tree's base version has been updated to v4.19-st7. The trees are up-to-date with kernel 5.4.296.

You can get this release via the git tree or as a tarball from https://mirrors.edge.kernel.org/pub/linux/kernel/projects/cip/4.19/

  v4.19.325-cip123:
    repository:
      https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
    branch:
      linux-4.19.y-cip
    commit hash:
      1e9cb006c55b0164de79c50947377a71deca9975
    Fixed CVEs:
      CVE-2024-26644: btrfs: don't abort filesystem when attempting to snapshot deleted subvolume
      CVE-2024-49935: ACPI: PAD: fix crash in exit_round_robin()
      CVE-2025-38102: VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify
      CVE-2025-38211: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction
      CVE-2025-38226: media: vivid: Change the siize of the composing
      CVE-2025-38230: jfs: validate AG parameters in dbMount() to prevent crashes
      CVE-2025-38245: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().
      CVE-2025-38249: ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3()
      CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty
      CVE-2025-38377: rose: fix dangling neighbour pointers in rose_rt_device_down()
      CVE-2025-38386: ACPICA: Refuse to evaluate a method if arguments are missing
      CVE-2025-38391: usb: typec: altmodes/displayport: do not index invalid pin_assignments
      CVE-2025-38401: mtk-sd: Prevent memory corruption from DMA map failure
      CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it
      CVE-2025-38406: wifi: ath6kl: remove WARN on bad firmware input
      CVE-2025-38445: md/raid1: Fix stack memory use after return in raid1_reshape
      CVE-2025-38448: usb: gadget: u_serial: Fix race condition in TTY wakeup
      CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist
      CVE-2025-38458: atm: clip: Fix NULL pointer dereference in vcc_sendmsg()
      CVE-2025-38459: atm: clip: Fix infinite recursive call of clip_push().
      CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd().
      CVE-2025-38464: tipc: Fix use-after-free in tipc_conn_close().
      CVE-2025-38465: netlink: Fix wraparounds of sk->sk_rmem_alloc.
      CVE-2025-38404: usb: typec: displayport: Fix potential deadlock
      CVE-2025-38513: wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev()
      CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct
      CVE-2025-38515: drm/sched: Increment job count before swapping tail spsc queue
      CVE-2025-38540: HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras
      CVE-2025-38542: net: appletalk: Fix device refcount leak in atrtr_create()
      CVE-2025-38546: atm: clip: Fix memory leak of struct clip_vcc.

Best regards,
Ulrich Hecht

Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123

[Kazunori Kobayashi]

[-- Attachment #1: Type: text/plain, Size: 5369 bytes --]

Hi,

On 8/19/25 00:21, Ulrich Hecht via lists.cip-project.org wrote:
> Hi,
>
> the CIP kernel team has released Linux kernel v4.19.325-cip123. The linux-4.19.y-cip tree's base version has been updated to v4.19-st7. The trees are up-to-date with kernel 5.4.296.
>
> You can get this release via the git tree or as a tarball fromhttps://mirrors.edge.kernel.org/pub/linux/kernel/projects/cip/4.19/
>
>    v4.19.325-cip123:
>      repository:
>        https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
>      branch:
>        linux-4.19.y-cip
>      commit hash:
>        1e9cb006c55b0164de79c50947377a71deca9975
>      Fixed CVEs:
>        CVE-2024-26644: btrfs: don't abort filesystem when attempting to snapshot deleted subvolume
>        CVE-2024-49935: ACPI: PAD: fix crash in exit_round_robin()
>        CVE-2025-38102: VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify
>        CVE-2025-38211: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction
>        CVE-2025-38226: media: vivid: Change the siize of the composing
>        CVE-2025-38230: jfs: validate AG parameters in dbMount() to prevent crashes
>        CVE-2025-38245: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().
>        CVE-2025-38249: ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3()
>        CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty
>        CVE-2025-38377: rose: fix dangling neighbour pointers in rose_rt_device_down()
>        CVE-2025-38386: ACPICA: Refuse to evaluate a method if arguments are missing
>        CVE-2025-38391: usb: typec: altmodes/displayport: do not index invalid pin_assignments
>        CVE-2025-38401: mtk-sd: Prevent memory corruption from DMA map failure
>        CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it
>        CVE-2025-38406: wifi: ath6kl: remove WARN on bad firmware input
>        CVE-2025-38445: md/raid1: Fix stack memory use after return in raid1_reshape
>        CVE-2025-38448: usb: gadget: u_serial: Fix race condition in TTY wakeup
>        CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist
>        CVE-2025-38458: atm: clip: Fix NULL pointer dereference in vcc_sendmsg()
>        CVE-2025-38459: atm: clip: Fix infinite recursive call of clip_push().
>        CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd().
>        CVE-2025-38464: tipc: Fix use-after-free in tipc_conn_close().
>        CVE-2025-38465: netlink: Fix wraparounds of sk->sk_rmem_alloc.
>        CVE-2025-38404: usb: typec: displayport: Fix potential deadlock
>        CVE-2025-38513: wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev()
>        CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct
>        CVE-2025-38515: drm/sched: Increment job count before swapping tail spsc queue
>        CVE-2025-38540: HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras
>        CVE-2025-38542: net: appletalk: Fix device refcount leak in atrtr_create()
>        CVE-2025-38546: atm: clip: Fix memory leak of struct clip_vcc.
>
> Best regards,
> Ulrich Hecht
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#19754):https://lists.cip-project.org/g/cip-dev/message/19754
> Mute This Topic:https://lists.cip-project.org/mt/114765008/7669380
> Group Owner:cip-dev+owner@lists.cip-project.org
> Unsubscribe:https://lists.cip-project.org/g/cip-dev/unsub [kazunori.kobayashi@cybertrust.co.jp]
> -=-=-=-=-=-=-=-=-=-=-=-
>
I ran into the following compilation error with omap2plus_defconfig 
applied in this kernel version.

| 
/buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c: 
In function 'ccdc_lsc_config': | 
/buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:452:3: 
error: implicit declaration of function 'dma_sync_sgtable_for_cpu'; did 
you mean 'dma_sync_single_for_cpu'? 
[-Werror=implicit-function-declaration] | 
dma_sync_sgtable_for_cpu(isp->dev, &req->table.sgt, | 
^~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_cpu | CC [M] 
drivers/media/rc/keymaps/rc-avermedia-a16d.o | 
/buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:461:3: 
error: implicit declaration of function 'dma_sync_sgtable_for_device'; 
did you mean 'dma_sync_single_for_device'? 
[-Werror=implicit-function-declaration] | 
dma_sync_sgtable_for_device(isp->dev, &req->table.sgt, | 
^~~~~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_device

It seems caused by the following change.

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/3483db997d491ba78957eb04743f6bb2ecc242aa

This change seems merged from the 5.4 based kernel, but some other 
dependencies would also be needed to pass the compilation.

Regards,
Kazunori

-- 
Kazunori Kobayashi
Cybertrust Japan Co., Ltd.
https://www.cybertrust.co.jp/

[-- Attachment #2: Type: text/html, Size: 7566 bytes --]

Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123

[Jan Kiszka]

On 03.09.25 08:31, Kazunori Kobayashi wrote:
> Hi,
> 
> On 8/19/25 00:21, Ulrich Hecht via lists.cip-project.org wrote:
>> Hi,
>>
>> the CIP kernel team has released Linux kernel v4.19.325-cip123. The linux-4.19.y-cip tree's base version has been updated to v4.19-st7. The trees are up-to-date with kernel 5.4.296.
>>
>> You can get this release via the git tree or as a tarball from https://mirrors.edge.kernel.org/pub/linux/kernel/projects/cip/4.19/
>>
>>   v4.19.325-cip123:
>>     repository:
>>       https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
>>     branch:
>>       linux-4.19.y-cip
>>     commit hash:
>>       1e9cb006c55b0164de79c50947377a71deca9975
>>     Fixed CVEs:
>>       CVE-2024-26644: btrfs: don't abort filesystem when attempting to snapshot deleted subvolume
>>       CVE-2024-49935: ACPI: PAD: fix crash in exit_round_robin()
>>       CVE-2025-38102: VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify
>>       CVE-2025-38211: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction
>>       CVE-2025-38226: media: vivid: Change the siize of the composing
>>       CVE-2025-38230: jfs: validate AG parameters in dbMount() to prevent crashes
>>       CVE-2025-38245: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().
>>       CVE-2025-38249: ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3()
>>       CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty
>>       CVE-2025-38377: rose: fix dangling neighbour pointers in rose_rt_device_down()
>>       CVE-2025-38386: ACPICA: Refuse to evaluate a method if arguments are missing
>>       CVE-2025-38391: usb: typec: altmodes/displayport: do not index invalid pin_assignments
>>       CVE-2025-38401: mtk-sd: Prevent memory corruption from DMA map failure
>>       CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it
>>       CVE-2025-38406: wifi: ath6kl: remove WARN on bad firmware input
>>       CVE-2025-38445: md/raid1: Fix stack memory use after return in raid1_reshape
>>       CVE-2025-38448: usb: gadget: u_serial: Fix race condition in TTY wakeup
>>       CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist
>>       CVE-2025-38458: atm: clip: Fix NULL pointer dereference in vcc_sendmsg()
>>       CVE-2025-38459: atm: clip: Fix infinite recursive call of clip_push().
>>       CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd().
>>       CVE-2025-38464: tipc: Fix use-after-free in tipc_conn_close().
>>       CVE-2025-38465: netlink: Fix wraparounds of sk->sk_rmem_alloc.
>>       CVE-2025-38404: usb: typec: displayport: Fix potential deadlock
>>       CVE-2025-38513: wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev()
>>       CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct
>>       CVE-2025-38515: drm/sched: Increment job count before swapping tail spsc queue
>>       CVE-2025-38540: HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras
>>       CVE-2025-38542: net: appletalk: Fix device refcount leak in atrtr_create()
>>       CVE-2025-38546: atm: clip: Fix memory leak of struct clip_vcc.
>>
>> Best regards,
>> Ulrich Hecht
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#19754): https://lists.cip-project.org/g/cip-dev/message/19754
>> Mute This Topic: https://lists.cip-project.org/mt/114765008/7669380
>> Group Owner: cip-dev+owner@lists.cip-project.org
>> Unsubscribe: https://lists.cip-project.org/g/cip-dev/unsub [kazunori.kobayashi@cybertrust.co.jp]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
> I ran into the following compilation error with omap2plus_defconfig
> applied in this kernel version.
> 
> | /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/
> build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/
> am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c: In
> function 'ccdc_lsc_config': | /buildbot/
> build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-
> evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/
> kernel-source/drivers/media/platform/omap3isp/ispccdc.c:452:3: error:
> implicit declaration of function 'dma_sync_sgtable_for_cpu'; did you
> mean 'dma_sync_single_for_cpu'? [-Werror=implicit-function-declaration]
> | dma_sync_sgtable_for_cpu(isp->dev, &req->table.sgt, |
> ^~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_cpu | CC [M] drivers/
> media/rc/keymaps/rc-avermedia-a16d.o | /buildbot/
> build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-
> evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/
> kernel-source/drivers/media/platform/omap3isp/ispccdc.c:461:3: error:
> implicit declaration of function 'dma_sync_sgtable_for_device'; did you
> mean 'dma_sync_single_for_device'? [-Werror=implicit-function-
> declaration] | dma_sync_sgtable_for_device(isp->dev, &req->table.sgt, |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_device
> 

Hah, now I can read it while replying to it in plaintext. ;)

> It seems caused by the following change.
> 
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/
> commit/3483db997d491ba78957eb04743f6bb2ecc242aa
> 
> This change seems merged from the 5.4 based kernel, but some other
> dependencies would also be needed to pass the compilation.
> 

General question: Is that build breakage above not triggerable via the
cip-kernel-configs? If so, you likely want to make sure that it is. If
it was triggerable already, then we should try to understand why it was
missed.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123

[Ulrich Hecht]

> On 09/03/2025 12:36 PM CEST Jan Kiszka via lists.cip-project.org <jan.kiszka=siemens.com@lists.cip-project.org> wrote:
> General question: Is that build breakage above not triggerable via the
> cip-kernel-configs?

CONFIG_VIDEO_OMAP3 is not enabled in any CIP configs.

> If so, you likely want to make sure that it is. If
> it was triggerable already, then we should try to understand why it was
> missed.

We could enable all the defconfigs; I think that discussion has already happened some time ago, though I don't remember the outcome. :)

I keep a bunch of local configs that cover all sorts of unsupported stuff (m68k etc.) that I build before pushing a kernel to make sure nothing breaks needlessly. I have added omap2plus_defconfig to that.

CU
Uli

Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123

[Jan Kiszka]

On 03.09.25 16:46, Ulrich Hecht wrote:
> 
>> On 09/03/2025 12:36 PM CEST Jan Kiszka via lists.cip-project.org <jan.kiszka=siemens.com@lists.cip-project.org> wrote:
>> General question: Is that build breakage above not triggerable via the
>> cip-kernel-configs?
> 
> CONFIG_VIDEO_OMAP3 is not enabled in any CIP configs.

I suspected that :) - then it is formally not supported what is likely
not the intended state...

> 
>> If so, you likely want to make sure that it is. If
>> it was triggerable already, then we should try to understand why it was
>> missed.
> 
> We could enable all the defconfigs; I think that discussion has already happened some time ago, though I don't remember the outcome. :)
> 
> I keep a bunch of local configs that cover all sorts of unsupported stuff (m68k etc.) that I build before pushing a kernel to make sure nothing breaks needlessly. I have added omap2plus_defconfig to that.

My point here is to remember everyone that we are formally (and here
also practically) defining our support and test scope of the CIP kernels
via the publicly available defconfigs.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123

[Ulrich Hecht]

> On 09/03/2025 8:31 AM CEST Kazunori Kobayashi via lists.cip-project.org > I ran into the following compilation error with omap2plus_defconfig applied in this kernel version.
> | /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c: In function 'ccdc_lsc_config': | /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:452:3: error: implicit declaration of function 'dma_sync_sgtable_for_cpu'; did you mean 'dma_sync_single_for_cpu'? [-Werror=implicit-function-declaration] | dma_sync_sgtable_for_cpu(isp->dev, &req->table.sgt, | ^~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_cpu | CC [M] drivers/media/rc/keymaps/rc-avermedia-a16d.o | /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am335x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-evmsk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:461:3: error: implicit declaration of function 'dma_sync_sgtable_for_device'; did you mean 'dma_sync_single_for_device'? [-Werror=implicit-function-declaration] | dma_sync_sgtable_for_device(isp->dev, &req->table.sgt, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_device
> It seems caused by the following change.
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/3483db997d491ba78957eb04743f6bb2ecc242aa
> This change seems merged from the 5.4 based kernel, but some other dependencies would also be needed to pass the compilation.

Thanks for the report.

Looks like it's missing "dma-mapping: add generic helpers for mapping sgtable objects". I pushed a backport to the rc tree (https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-st-rc), please check if it works.

I have also added omap2plus_defconfig to my local build configs.

CU
Uli

RE: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123

[nobuhiro.iwamatsu.x90]

Hi,

> -----Original Message-----
> From: Ulrich Hecht <uli@fpond.eu>
> Sent: Wednesday, September 3, 2025 11:39 PM
> To: kazunori.kobayashi@miraclelinux.com; cip-dev@lists.cip-project.org;
> pavel@denx.de; jan.kiszka@siemens.com; masami.ichikawa@cybertrust.co.jp;
> chris.paterson2@renesas.com; iwamatsu nobuhiro(岩松 信洋 □ＤＩＴＣ○Ｃ
> ＰＴ) <nobuhiro.iwamatsu.x90@mail.toshiba>
> Subject: Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123
> 
> 
> > On 09/03/2025 8:31 AM CEST Kazunori Kobayashi via lists.cip-project.org >
> I ran into the following compilation error with omap2plus_defconfig applied in
> this kernel version.
> > |
> /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am3
> > |
> 35x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-ev
> m
> > | sk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c: In
> > | function 'ccdc_lsc_config': |
> > |
> /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am3
> > |
> 35x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-ev
> m
> > | sk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:452:3:
> > | error: implicit declaration of function 'dma_sync_sgtable_for_cpu';
> > | did you mean 'dma_sync_single_for_cpu'?
> > | [-Werror=implicit-function-declaration] |
> > | dma_sync_sgtable_for_cpu(isp->dev, &req->table.sgt, |
> > | ^~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_cpu | CC
> [M]
> > | drivers/media/rc/keymaps/rc-avermedia-a16d.o |
> > |
> /buildbot/build_daily_emlinux_am335xevmsk_latest_dev/build/build_am3
> > |
> 35x-evmsk_emlinux_core-image-weston/tmp-glibc/work-shared/am335x-ev
> m
> > | sk/kernel-source/drivers/media/platform/omap3isp/ispccdc.c:461:3:
> > | error: implicit declaration of function
> > | 'dma_sync_sgtable_for_device'; did you mean
> > | 'dma_sync_single_for_device'?
> > | [-Werror=implicit-function-declaration] |
> > | dma_sync_sgtable_for_device(isp->dev, &req->table.sgt, |
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ | dma_sync_single_for_device
> > It seems caused by the following change.
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/3483db997
> > d491ba78957eb04743f6bb2ecc242aa This change seems merged from the
> 5.4
> > based kernel, but some other dependencies would also be needed to pass
> the compilation.
> 
> Thanks for the report.
> 
> Looks like it's missing "dma-mapping: add generic helpers for mapping sgtable
> objects". I pushed a backport to the rc tree
> (https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=lin
> ux-4.19.y-st-rc), please check if it works.
> 
> I have also added omap2plus_defconfig to my local build configs.
> 

Another approach is to build the architecture's defconfig (aliased as multi_v7_defconfig for arm)
along with allyesconfig and allmodconfig. This should resolve most build errors on armhf(debian) devices.

Best regards,
  Nobuhiro

Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123

[Kazunori Kobayashi]

On 9/3/25 23:38, Ulrich Hecht wrote:
> Thanks for the report.
>
> Looks like it's missing "dma-mapping: add generic helpers for mapping sgtable objects". I pushed a backport to the rc tree (https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-st-rc), please check if it works.
>
> I have also added omap2plus_defconfig to my local build configs.
>
> CU
> Uli

Thank you. I could confirm the compilation with CONFIG_VIDEO_OMAP3 
enabled was passed with this backported patch.

We, the Cybertrust OSS development team, realized CONFIG_VIDEO_OMAP3 is 
out of scope of the CIP kernel in this post. Currently we are discussing 
if we have to continue using this config and propose cip-kernel-config 
supports it in a formal way. We will contact you separately if needed.

Regards,
Kazunori

-- 
Kazunori Kobayashi
Cybertrust Japan Co., Ltd.
https://www.cybertrust.co.jp/