netdev - Re: [net-next] WARNING: CPU: 2 PID: 1189 at ../net/core/skbuff.c:5412 skb_try

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 06 Aug 2021 09:53:41 +0200
From:   Paolo Abeni <pabeni@...hat.com>
To:     Grygorii Strashko <grygorii.strashko@...com>,
        netdev <netdev@...r.kernel.org>
Subject: Re: [net-next] WARNING: CPU: 2 PID: 1189 at
 ../net/core/skbuff.c:5412 skb_try_coalesce+0x354/0x368

Hello,

On Thu, 2021-08-05 at 22:04 +0300, Grygorii Strashko wrote:
> with current net-next is see below splat when run netperf TCP_STREAM
> 
> <REMOTE HOST> netperf -l 10 -H 192.168.1.2 -t TCP_STREAM -c -C -j -B "am6 " -s 1 -s 1
> 
> Is this know issue?
> 
> <FAILED DUT>
> root@...5xx-evm:~# uname -a
> Linux am65xx-evm 5.14.0-rc3-00973-g372bbdd5bb3f #5 SMP PREEMPT Thu Aug 5 21:57:28 EEST 2021 aarch64 GNU/Linux
> 
> root@...5xx-evm:~# [  227.929271] ------------[ cut here ]------------
> [  227.933917] WARNING: CPU: 2 PID: 1189 at ../net/core/skbuff.c:5412 skb_try_coalesce+0x354/0x368
> [  227.942624] Modules linked in:
> [  227.945679] CPU: 2 PID: 1189 Comm: netserver Not tainted 5.14.0-rc3-00973-g372bbdd5bb3f #5
> [  227.953931] Hardware name: Texas Instruments AM654 Base Board (DT)
> [  227.960098] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
> [  227.966097] pc : skb_try_coalesce+0x354/0x368
> [  227.970449] lr : tcp_try_coalesce.part.74+0x48/0x180
> [  227.975410] sp : ffff80001544fa40
> [  227.978716] x29: ffff80001544fa40 x28: ffff0008013a0dc0 x27: 0000000000000000
> [  227.985851] x26: 0000000000000000 x25: 0000000000002d20 x24: ffff000809f25240
> [  227.992984] x23: ffff000809f286c0 x22: 0000000000002d40 x21: ffff80001544fac4
> [  228.000118] x20: ffff000807536600 x19: ffff000807535800 x18: 0000000000000000
> [  228.007251] x17: 0000000000000000 x16: 0000000000000000 x15: ffff00080794a882
> [  228.014384] x14: 72657074656e0066 x13: 0000000000000080 x12: ffff000800792e58
> [  228.021517] x11: 0000000000000000 x10: 0000000000000001 x9 : ffff000000000000
> [  228.028650] x8 : 0000000000002798 x7 : 00000000000005a8 x6 : ffff000809f24c82
> [  228.035783] x5 : 0000000000000000 x4 : 0000000000000640 x3 : 0000000000000001
> [  228.042915] x2 : ffff80001544fb57 x1 : 0000000000000007 x0 : ffff000809f286c0
> [  228.050050] Call trace:
> [  228.052490]  skb_try_coalesce+0x354/0x368
> [  228.056497]  tcp_try_coalesce.part.74+0x48/0x180
> [  228.061108]  tcp_queue_rcv+0x12c/0x170
> [  228.064853]  tcp_rcv_established+0x558/0x6f8
> [  228.069118]  tcp_v4_do_rcv+0x90/0x220
> [  228.072775]  __release_sock+0x70/0xb8
> [  228.076439]  release_sock+0x30/0x90
> [  228.079926]  tcp_recvmsg+0x90/0x1d0
> [  228.083411]  inet_recvmsg+0x54/0x128
> [  228.086983]  __sys_recvfrom+0xbc/0x148
> [  228.090728]  __arm64_sys_recvfrom+0x24/0x38
> [  228.094906]  invoke_syscall+0x44/0x100
> [  228.098655]  el0_svc_common+0x3c/0xd8
> [  228.102314]  do_el0_svc+0x28/0x90
> [  228.105626]  el0_svc+0x24/0x38
> [  228.108679]  el0t_64_sync_handler+0x90/0xb8
> [  228.112857]  el0t_64_sync+0x178/0x17c
> [  228.116517] ---[ end trace 2e0ec9d02424634a ]---        .0

The above should be fixed by the net-next
commit af352460b465d7a8afbeb3be07c0268d1d48a4d7

Could you please have a shot at that?

Thanks!

Paolo