Hi all,

CIP kernel team has released Linux kernel v4.19.259-cip82 v5.10.145-cip17.
The linux-4.19.y-cip tree has been updated base version from v4.19.257 to
v4.19.259, and the linux-5.10.y-cip tree has been updated base version from
v5.10.140 to v5.10.145.

You can get this release via the git tree at:

v4.19.259-cip82:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.19.y-cip
commit hash:
91f283faebd1a92efc2cfe0a3de7c568c87e5ee5
Fixed CVEs:
- CVE-2022-2663 netfilter: nf_conntrack_irc: Fix forged IP logic
- CVE-2022-40307 efi: capsule-loader: Fix use-after-free in efi_capsule_write
added commits:
CIP: Bump version suffix to -cip82 after merge from stable

v5.10.145-cip17:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-5.10.y-cip
commit hash:
93a53e86925ce8c2e0608e173e2c7b952ee61cdd
Fixed CVEs:
- CVE-2022-2663 netfilter: nf_conntrack_irc: Fix forged IP logic
- CVE-2022-40307 efi: capsule-loader: Fix use-after-free in efi_capsule_write
added commits:
CIP: Bump version suffix to -cip17 after merge from stable

Best regards,
Nobuhiro

On Mon, 2022-09-26 at 08:09 +0000, Nobuhiro Iwamatsu via lists.cip-
project.org wrote:

Hi all,

CIP kernel team has released Linux kernel v4.19.259-cip82 v5.10.145-cip17.
The linux-4.19.y-cip tree has been updated base version from v4.19.257 to
v4.19.259, and the linux-5.10.y-cip tree has been updated base version from
v5.10.140 to v5.10.145.

You can get this release via the git tree at:

v4.19.259-cip82:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git

Nope. The git tree hasn't been updated yet, or is this kind of delay
expected (mirroring)?

FYI: The locking bug (deadlock) below was observed on v4.19.257-cip81
and will be fixed by v4.19.259-cip82 as the necessary fix comes from
v4.19.259.

Faulty commit (since v.4.19.238):

242a3e0c75b6 ("SUNRPC: avoid race between mod_timer() and del_timer_sync()")

Fix (since v4.19.259):

bcab4d551a3d ("SUNRPC: use _bh spinlocking on ->transport_lock")

Best regards,
Florian

Log:
[ 12.400442] ================================
[ 12.404706] WARNING: inconsistent lock state
[ 12.408969] 4.19.257-cip81+ #1 Not tainted
[ 12.412538] --------------------------------
[ 12.416802] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
[ 12.422804] kworker/u8:2/73 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 12.428287] 00000000e6196caf (&(&xprt->transport_lock)->rlock){+.?.}, at: xprt_destroy+0x55/0xd0
[ 12.437078] {IN-SOFTIRQ-W} state was registered at:
[ 12.441953] lock_acquire+0x8d/0x1a0
[ 12.445612] _raw_spin_lock+0x2f/0x40
[ 12.449356] xs_tcp_state_change+0xe8/0x2c0
[ 12.453622] tcp_rcv_synsent_state_process+0x23b/0x700
[ 12.458844] tcp_rcv_state_process+0x165/0x990
[ 12.463368] tcp_v4_do_rcv+0xb4/0x1e0
[ 12.467111] tcp_v4_rcv+0xa86/0xb80
[ 12.470680] ip_local_deliver_finish+0x8d/0x260
[ 12.475295] __netif_receive_skb_one_core+0x5a/0x80
[ 12.480252] netif_receive_skb_internal+0x8e/0x250
[ 12.485123] napi_gro_receive+0xda/0x1b0
[ 12.489128] igb_clean_rx_irq+0x2b9/0x540
[ 12.493222] igb_poll+0x3d/0x2b0
[ 12.496528] net_rx_action+0x103/0x430
[ 12.500361] __do_softirq+0xec/0x4a3
[ 12.504019] irq_exit+0x111/0x120
[ 12.507415] do_IRQ+0xb7/0x150
[ 12.510549] ret_from_intr+0x0/0x1d
[ 12.514118] mwait_idle+0x93/0x210
[ 12.517600] default_idle_call+0x2b/0x30
[ 12.521606] cpuidle_idle_call+0x134/0x1a0
[ 12.525785] do_idle+0x72/0xc0
[ 12.528920] cpu_startup_entry+0x6c/0x70
[ 12.532929] start_secondary+0x18b/0x1c0
[ 12.536935] secondary_startup_64+0xa4/0xb0
[ 12.541196] irq event stamp: 3499
[ 12.544509] hardirqs last enabled at (3499): [<ffffffff81296749>] cmpxchg_double_slab.constprop.0.isra.0+0x199/0x1d0
[ 12.555116] hardirqs last disabled at (3498): [<ffffffff8129660d>] cmpxchg_double_slab.constprop.0.isra.0+0x5d/0x1d0
[ 12.565633] softirqs last enabled at (3480): [<ffffffff8198c238>] rpc_wake_up_first_on_wq+0x78/0x180
[ 12.574847] softirqs last disabled at (3478): [<ffffffff8198c1e1>] rpc_wake_up_first_on_wq+0x21/0x180
[ 12.584062]
[ 12.584062] other info that might help us debug this:
[ 12.590582] Possible unsafe locking scenario:
[ 12.590582]
[ 12.596497] CPU0
[ 12.598935] ----
[ 12.601376] lock(&(&xprt->transport_lock)->rlock);
[ 12.606336] <Interrupt>
[ 12.608949] lock(&(&xprt->transport_lock)->rlock);
[ 12.614081]
[ 12.614081] *** DEADLOCK ***
[ 12.614081]
[ 12.619995] 2 locks held by kworker/u8:2/73:
[ 12.624259] #0: 0000000040d0fe46 ((wq_completion)\"rpciod\"){+.+.}, at: process_one_work+0x1b1/0x5f0
[ 12.633307] #1: 000000004da2dce8 ((work_completion)(&task->u.tk_work)){+.+.}, at: process_one_work+0x1b1/0x5f0
[ 12.643390]
[ 12.643390] stack backtrace:
[ 12.647744] CPU: 3 PID: 73 Comm: kworker/u8:2 Not tainted 4.19.257+ #1
[ 12.654264] Hardware name: SIEMENS AG SIMATIC IPC227E/A5E42630598, BIOS V20.01.11 03/15/2018
[ 12.662697] Workqueue: rpciod rpc_async_schedule
[ 12.667310] Call Trace:
[ 12.669759] dump_stack+0x71/0x98
[ 12.673072] print_usage_bug.cold+0x191/0x19a
[ 12.677427] ? print_shortest_lock_dependencies+0x40/0x40
[ 12.682822] mark_lock_irq+0x178/0x280
[ 12.686564] mark_lock+0x12e/0x3f0
[ 12.689965] mark_irqflags+0xe8/0x100
[ 12.693624] __lock_acquire+0x1cd/0xaa0
[ 12.697454] ? __slab_free+0xa0/0x220
[ 12.701114] lock_acquire+0x8d/0x1a0
[ 12.704686] ? xprt_destroy+0x55/0xd0
[ 12.708343] _raw_spin_lock+0x2f/0x40
[ 12.712001] ? xprt_destroy+0x55/0xd0
[ 12.715659] xprt_destroy+0x55/0xd0
[ 12.719145] __rpc_execute+0x237/0x360
[ 12.722893] process_one_work+0x239/0x5f0
[ 12.726901] worker_thread+0x52/0x3b0
[ 12.730560] ? rescuer_thread+0x3a0/0x3a0
[ 12.734565] kthread+0x142/0x160
[ 12.737788] ? kthread_insert_work_sanity_check+0x50/0x50
[ 12.743180] ret_from_fork+0x3a/0x50

Hi!

CIP kernel team has released Linux kernel v4.19.259-cip82 v5.10.145-cip17.
The linux-4.19.y-cip tree has been updated base version from v4.19.257 to
v4.19.259, and the linux-5.10.y-cip tree has been updated base version from
v5.10.140 to v5.10.145.

You can get this release via the git tree at:

v4.19.259-cip82:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git

Nope. The git tree hasn't been updated yet, or is this kind of delay
expected (mirroring)?

That would be a bit long for a delay, I guess this is a case of missed
push.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Hi all,

Hi!

The linux-4.19.y-cip tree has been updated base version from
v4.19.257 to v4.19.259, and the linux-5.10.y-cip tree has been
updated base version from
v5.10.140 to v5.10.145.

...

Right, I forgot to push to repository...
I pushed yesterday afternoon (14:00 JST), so it is updated.

I see the updates now.

There's good match of v5.10.145-cip17, v5.10.145-rt74, I'll likely get
advantage of that.

On 4.19 side, last -rt is Aug 13, Linux 4.19.255-rt113. I'd like
matchig -cip release when next 4.19-rt is released.

Thank you and best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany