All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ce5405b9159db688fa37@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, kernel@pengutronix.de,
	 kuba@kernel.org, linux-can@vger.kernel.org,
	linux-kernel@vger.kernel.org,  mkl@pengutronix.de,
	netdev@vger.kernel.org, o.rempel@pengutronix.de,
	 pabeni@redhat.com, robin@protonic.nl, socketcan@hartkopp.net,
	 syzkaller-bugs@googlegroups.com
Subject: [syzbot] [can?] WARNING in j1939_xtp_rx_rts (2)
Date: Mon, 06 May 2024 01:26:23 -0700	[thread overview]
Message-ID: <0000000000001fa3ce0617c4d3c1@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    cdc74c9d06e7 Merge branch 'gve-queue-api'
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17beea2f180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7c70a227bc928e1b
dashboard link: https://syzkaller.appspot.com/bug?extid=ce5405b9159db688fa37
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f0df1462721b/disk-cdc74c9d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7e5c38fb35eb/vmlinux-cdc74c9d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8b7652427355/bzImage-cdc74c9d.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ce5405b9159db688fa37@syzkaller.appspotmail.com

vxcan0: j1939_xtp_rx_abort_one: 0xffff888042069c00: 0x00000: (8) Duplicate sequence number (and software is not able to recover)
vxcan0: j1939_xtp_rx_abort_one: 0xffff88804206a000: 0x00000: (8) Duplicate sequence number (and software is not able to recover)
------------[ cut here ]------------
WARNING: CPU: 1 PID: 11 at net/can/j1939/transport.c:1656 j1939_xtp_rx_rts_session_new net/can/j1939/transport.c:1656 [inline]
WARNING: CPU: 1 PID: 11 at net/can/j1939/transport.c:1656 j1939_xtp_rx_rts+0x13db/0x1930 net/can/j1939/transport.c:1735
Modules linked in:
CPU: 1 PID: 11 Comm: kworker/u8:1 Not tainted 6.9.0-rc6-syzkaller-01478-gcdc74c9d06e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: krdsd rds_connect_worker
RIP: 0010:j1939_xtp_rx_rts_session_new net/can/j1939/transport.c:1656 [inline]
RIP: 0010:j1939_xtp_rx_rts+0x13db/0x1930 net/can/j1939/transport.c:1735
Code: e8 7a f6 8a f7 e9 d6 f1 ff ff 89 d9 80 e1 07 38 c1 0f 8c ea f1 ff ff 48 89 df e8 60 f6 8a f7 e9 dd f1 ff ff e8 06 fd 25 f7 90 <0f> 0b 90 e9 6d f2 ff ff 89 f9 80 e1 07 38 c1 0f 8c 51 ee ff ff 48
RSP: 0018:ffffc90000a08640 EFLAGS: 00010246
RAX: ffffffff8a702d7a RBX: 00000000fffffff5 RCX: ffff8880172abc00
RDX: 0000000080000100 RSI: 00000000fffffff5 RDI: 0000000000000000
RBP: ffffc90000a087a8 R08: ffffffff8a702aec R09: 1ffffffff25e80c6
R10: dffffc0000000000 R11: fffffbfff25e80c7 R12: dffffc0000000000
R13: ffff888042fab000 R14: 0000000000000014 R15: 00000000000007c6
FS:  0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c000461144 CR3: 000000007cc42000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <IRQ>
 j1939_tp_cmd_recv net/can/j1939/transport.c:2057 [inline]
 j1939_tp_recv+0xb84/0x1050 net/can/j1939/transport.c:2144
 j1939_can_recv+0x732/0xb20 net/can/j1939/main.c:112
 deliver net/can/af_can.c:572 [inline]
 can_rcv_filter+0x359/0x7f0 net/can/af_can.c:606
 can_receive+0x327/0x480 net/can/af_can.c:663
 can_rcv+0x144/0x260 net/can/af_can.c:687
 __netif_receive_skb_one_core net/core/dev.c:5625 [inline]
 __netif_receive_skb+0x2e0/0x650 net/core/dev.c:5739
 process_backlog+0x391/0x7d0 net/core/dev.c:6068
 __napi_poll+0xcb/0x490 net/core/dev.c:6722
 napi_poll net/core/dev.c:6791 [inline]
 net_rx_action+0x7bb/0x10a0 net/core/dev.c:6907
 __do_softirq+0x2c6/0x980 kernel/softirq.c:554
 invoke_softirq kernel/softirq.c:428 [inline]
 __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633
 irq_exit_rcu+0x9/0x30 kernel/softirq.c:645
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]
 sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
RIP: 0010:security_socket_create+0x6e/0xb0 security/security.c:4374
Code: 78 b8 97 fd 48 8b 1b 48 85 db 74 3b 48 8d 6b 18 48 89 e8 48 c1 e8 03 42 80 3c 30 00 74 08 48 89 ef e8 56 b8 97 fd 4c 8b 5d 00 <44> 89 ef 44 89 e6 44 89 fa 8b 4c 24 04 41 ff d3 66 90 85 c0 75 10
RSP: 0018:ffffc90000107948 EFLAGS: 00000246
RAX: 1ffffffff1bab1b8 RBX: ffffffff8dd58da8 RCX: ffff8880172abc00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffffffff8dd58dc0 R08: ffffffff8948d77b R09: 0000000000000001
R10: dffffc0000000000 R11: ffffffff846c8900 R12: 0000000000000001
R13: 0000000000000002 R14: dffffc0000000000 R15: 0000000000000006
 __sock_create+0xc9/0x920 net/socket.c:1526
 rds_tcp_conn_path_connect+0x2bb/0xbc0
 rds_connect_worker+0x1dd/0x2a0 net/rds/threads.c:176
 process_one_work kernel/workqueue.c:3267 [inline]
 process_scheduled_works+0xa10/0x17c0 kernel/workqueue.c:3348
 worker_thread+0x86d/0xd70 kernel/workqueue.c:3429
 kthread+0x2f0/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
----------------
Code disassembly (best guess):
   0:	78 b8                	js     0xffffffba
   2:	97                   	xchg   %eax,%edi
   3:	fd                   	std
   4:	48 8b 1b             	mov    (%rbx),%rbx
   7:	48 85 db             	test   %rbx,%rbx
   a:	74 3b                	je     0x47
   c:	48 8d 6b 18          	lea    0x18(%rbx),%rbp
  10:	48 89 e8             	mov    %rbp,%rax
  13:	48 c1 e8 03          	shr    $0x3,%rax
  17:	42 80 3c 30 00       	cmpb   $0x0,(%rax,%r14,1)
  1c:	74 08                	je     0x26
  1e:	48 89 ef             	mov    %rbp,%rdi
  21:	e8 56 b8 97 fd       	call   0xfd97b87c
  26:	4c 8b 5d 00          	mov    0x0(%rbp),%r11
* 2a:	44 89 ef             	mov    %r13d,%edi <-- trapping instruction
  2d:	44 89 e6             	mov    %r12d,%esi
  30:	44 89 fa             	mov    %r15d,%edx
  33:	8b 4c 24 04          	mov    0x4(%rsp),%ecx
  37:	41 ff d3             	call   *%r11
  3a:	66 90                	xchg   %ax,%ax
  3c:	85 c0                	test   %eax,%eax
  3e:	75 10                	jne    0x50


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2024-05-06  8:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0000000000001fa3ce0617c4d3c1@google.com \
    --to=syzbot+ce5405b9159db688fa37@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=robin@protonic.nl \
    --cc=socketcan@hartkopp.net \
    --cc=syzkaller-bugs@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.