netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+34dcf6bbda0e05f6b3ed@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, linux@rempel-privat.de,
	mkl@pengutronix.de, netdev@vger.kernel.org, pabeni@redhat.com,
	robin@protonic.nl, socketcan@hartkopp.net,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in j1939_tp_rxtimer (2)
Date: Sun, 11 Sep 2022 19:30:34 -0700	[thread overview]
Message-ID: <00000000000027774b05e871ae18@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    0066f1b0e275 afs: Return -EAGAIN, not -EREMOTEIO, when a f..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=124a4c8f080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5971bb33b0db1ef1
dashboard link: https://syzkaller.appspot.com/bug?extid=34dcf6bbda0e05f6b3ed
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, 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+34dcf6bbda0e05f6b3ed@syzkaller.appspotmail.com

WARNING: CPU: 0 PID: 15 at net/can/j1939/transport.c:1096 j1939_session_deactivate_activate_next net/can/j1939/transport.c:1106 [inline]
WARNING: CPU: 0 PID: 15 at net/can/j1939/transport.c:1096 j1939_tp_rxtimer+0x821/0xa20 net/can/j1939/transport.c:1234
Modules linked in:
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.0.0-rc4-syzkaller-00062-g0066f1b0e275 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
RIP: 0010:j1939_session_deactivate net/can/j1939/transport.c:1096 [inline]
RIP: 0010:j1939_session_deactivate_activate_next net/can/j1939/transport.c:1106 [inline]
RIP: 0010:j1939_tp_rxtimer+0x821/0xa20 net/can/j1939/transport.c:1234
Code: e8 c4 62 44 f8 48 8b 3c 24 e9 0a f9 ff ff e8 b6 62 44 f8 4c 89 f7 be 03 00 00 00 e8 79 7f f0 fa e9 52 f9 ff ff e8 9f 62 44 f8 <0f> 0b e9 fa f9 ff ff e8 93 62 44 f8 0f 0b e9 21 fb ff ff e8 87 62
RSP: 0018:ffffc90000147a90 EFLAGS: 00010246
RAX: ffffffff89453641 RBX: 0000000000000001 RCX: ffff8880122e3b00
RDX: 0000000000000301 RSI: 0000000000000001 RDI: 0000000000000002
RBP: dffffc0000000000 R08: ffffffff89453034 R09: ffffed100f764506
R10: ffffed100f764506 R11: 1ffff1100f764505 R12: 1ffff1100f764500
R13: ffff88807bb22800 R14: 1ffff1100f76451b R15: ffff88807bb228d8
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001000 CR3: 000000001f158000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __run_hrtimer kernel/time/hrtimer.c:1685 [inline]
 __hrtimer_run_queues+0x50b/0xa60 kernel/time/hrtimer.c:1749
 hrtimer_run_softirq+0x1a1/0x580 kernel/time/hrtimer.c:1766
 __do_softirq+0x382/0x793 kernel/softirq.c:571
 run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
 smpboot_thread_fn+0x533/0x9d0 kernel/smpboot.c:164
 kthread+0x266/0x300 kernel/kthread.c:376
 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:[~2022-09-12  2:30 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=00000000000027774b05e871ae18@google.com \
    --to=syzbot+34dcf6bbda0e05f6b3ed@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=linux@rempel-privat.de \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).