public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Kazunori Kobayashi <kazunori.kobayashi@miraclelinux.com>
To: uli@fpond.eu,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"pavel@denx.de" <pavel@denx.de>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"masami.ichikawa@cybertrust.co.jp"
	<masami.ichikawa@cybertrust.co.jp>,
	"chris.paterson2@renesas.com" <chris.paterson2@renesas.com>,
	"nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip123
Date: Wed, 3 Sep 2025 15:31:24 +0900	[thread overview]
Message-ID: <42de8250-d98b-40e5-9e8a-d6bbb1ca8b6b@miraclelinux.com> (raw)
In-Reply-To: <1602384696.84101.1755530487321@webmail.strato.de>

[-- 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 --]

  reply	other threads:[~2025-09-03  6:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 15:21 [ANNOUNCE] Release v4.19.325-cip123 Ulrich Hecht
2025-09-03  6:31 ` Kazunori Kobayashi [this message]
2025-09-03 10:36   ` [cip-dev] " Jan Kiszka
2025-09-03 14:46     ` Ulrich Hecht
2025-09-03 16:21       ` Jan Kiszka
2025-09-03 14:38   ` Ulrich Hecht
2025-09-03 23:35     ` nobuhiro.iwamatsu.x90
2025-09-04  3:32     ` Kazunori Kobayashi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42de8250-d98b-40e5-9e8a-d6bbb1ca8b6b@miraclelinux.com \
    --to=kazunori.kobayashi@miraclelinux.com \
    --cc=chris.paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=masami.ichikawa@cybertrust.co.jp \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    --cc=uli@fpond.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox