From: syzbot <syzbot+23df5d97f6d7d7e8a71c@syzkaller.appspotmail.com>
To: davem@davemloft.net, kernel@pengutronix.de, kuba@kernel.org,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@rempel-privat.de, mkl@pengutronix.de,
netdev@vger.kernel.org, robin@protonic.nl,
socketcan@hartkopp.net, syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in j1939_tp_rxtimer
Date: Tue, 16 Nov 2021 08:23:20 -0800 [thread overview]
Message-ID: <000000000000fbc35e05d0ea57a3@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 5833291ab6de Merge tag 'pci-v5.16-fixes-1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1125a676b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2897a869f0607967
dashboard link: https://syzkaller.appspot.com/bug?extid=23df5d97f6d7d7e8a71c
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+23df5d97f6d7d7e8a71c@syzkaller.appspotmail.com
vcan0: j1939_xtp_rx_dat: no rx connection found
vcan0: j1939_xtp_rx_dat_one: 0xffff8880261c9c00: last 00
vcan0: j1939_xtp_rx_dat: no rx connection found
vcan0: j1939_tp_rxtimer: 0xffff8880261cd800: abort rx timeout. Force session deactivation
------------[ cut here ]------------
WARNING: CPU: 1 PID: 20 at net/can/j1939/transport.c:1090 j1939_session_deactivate net/can/j1939/transport.c:1090 [inline]
WARNING: CPU: 1 PID: 20 at net/can/j1939/transport.c:1090 j1939_session_deactivate_activate_next net/can/j1939/transport.c:1100 [inline]
WARNING: CPU: 1 PID: 20 at net/can/j1939/transport.c:1090 j1939_tp_rxtimer+0x821/0xa20 net/can/j1939/transport.c:1228
Modules linked in:
CPU: 1 PID: 20 Comm: kworker/1:0 Not tainted 5.15.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_long defense_work_handler
RIP: 0010:j1939_session_deactivate net/can/j1939/transport.c:1090 [inline]
RIP: 0010:j1939_session_deactivate_activate_next net/can/j1939/transport.c:1100 [inline]
RIP: 0010:j1939_tp_rxtimer+0x821/0xa20 net/can/j1939/transport.c:1228
Code: e8 14 d1 6c f8 48 8b 3c 24 e9 0a f9 ff ff e8 06 d1 6c f8 4c 89 f7 be 03 00 00 00 e8 69 20 fe fa e9 52 f9 ff ff e8 ef d0 6c f8 <0f> 0b e9 fa f9 ff ff e8 e3 d0 6c f8 0f 0b e9 21 fb ff ff e8 d7 d0
RSP: 0018:ffffc90000dc0cb0 EFLAGS: 00010246
RAX: ffffffff89178381 RBX: 0000000000000001 RCX: ffff888012108000
RDX: 0000000000000302 RSI: 0000000000000001 RDI: 0000000000000002
RBP: dffffc0000000000 R08: ffffffff89177d74 R09: ffffed1004c39b06
R10: ffffed1004c39b06 R11: 0000000000000000 R12: 1ffff11004c39b00
R13: ffff8880261cd800 R14: 1ffff11004c39b1b R15: ffff8880261cd8d8
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f15f1427000 CR3: 00000000519fa000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x50b/0xa60 kernel/time/hrtimer.c:1749
hrtimer_run_softirq+0x1b7/0x5d0 kernel/time/hrtimer.c:1766
__do_softirq+0x392/0x7a3 kernel/softirq.c:558
do_softirq+0x161/0x240 kernel/softirq.c:459
</IRQ>
<TASK>
__local_bh_enable_ip+0x1b0/0x1f0 kernel/softirq.c:383
update_defense_level+0x878/0xc90 net/netfilter/ipvs/ip_vs_ctl.c:211
defense_work_handler+0x1c/0xd0 net/netfilter/ipvs/ip_vs_ctl.c:236
process_one_work+0x853/0x1140 kernel/workqueue.c:2298
worker_thread+0xac1/0x1320 kernel/workqueue.c:2445
kthread+0x468/0x490 kernel/kthread.c:327
ret_from_fork+0x1f/0x30
</TASK>
---
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.
reply other threads:[~2021-11-16 16:23 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=000000000000fbc35e05d0ea57a3@google.com \
--to=syzbot+23df5d97f6d7d7e8a71c@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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.