All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a76d93c00034a9fd23f5@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] panic: runtime error: floating point error (2)
Date: Tue, 25 Jul 2023 01:02:56 -0700	[thread overview]
Message-ID: <000000000000a33bfc06014b28c9@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    46670259519f Merge tag 'for-6.5-rc2-tag' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b2e452a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a4507c291b5ab5d4
dashboard link: https://syzkaller.appspot.com/bug?extid=a76d93c00034a9fd23f5
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13213daea80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f3b4b06a5f02/disk-46670259.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4db334f36495/vmlinux-46670259.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5977e704aeb2/bzImage-46670259.xz

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

2023/07/21 06:55:36 executed programs: 1794
2023/07/21 06:55:42 executed programs: 1851
2023/07/21 06:55:47 executed programs: 1914
2023/07/21 06:55:52 executed programs: 1976
2023/07/21 06:55:57 executed programs: 2046
panic: runtime error: floating point error
[signal SIGFPE: floating-point exception code=0x80 addr=0x0 pc=0x561291]

goroutine 22 [running]:
github.com/google/syzkaller/prog.ArgCommon.Type(...)
	/syzkaller/gopath/src/github.com/google/syzkaller/prog/prog.go:61
github.com/google/syzkaller/prog.(*ConstArg).Size(0xc9f428?)
	/syzkaller/gopath/src/github.com/google/syzkaller/prog/prog.go:79 +0x91
github.com/google/syzkaller/prog.foreachArgImpl({0xc9f4a8?, 0xc000fdba80?}, 0xc000873e80, 0xc00107fbb8)
	/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:152 +0x3ca
github.com/google/syzkaller/prog.foreachArgImpl({0xc9f4e8?, 0xc00008aae0?}, 0xc000873e80, 0xc00107fbb8)
	/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:168 +0x2ce
github.com/google/syzkaller/prog.ForeachArg(0xc00028eb90, 0x46734e?)
	/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:127 +0xde
github.com/google/syzkaller/prog.(*Prog).FallbackSignal(0xc001018b00, {0xc00086d180, 0x8, 0x0?})
	/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:249 +0x275
github.com/google/syzkaller/pkg/ipc.addFallbackSignal(0xc0005001c0?, 0xc000857bc0)
	/syzkaller/gopath/src/github.com/google/syzkaller/pkg/ipc/ipc.go:321 +0x146
github.com/google/syzkaller/pkg/ipc.(*Env).Exec(0xc00027c630, 0x0?, 0xc001018b00)
	/syzkaller/gopath/src/github.com/google/syzkaller/pkg/ipc/ipc.go:295 +0x359
main.(*Context).execute(0xc0005000e0, 0x0?, 0x0?, 0x0?)
	/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:171 +0x146
main.(*Context).run(0xc0005000e0, 0x0?)
	/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:156 +0xc5
main.main.func3()
	/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:119 +0x5c
created by main.main
	/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:117 +0x588


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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

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

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

                 reply	other threads:[~2023-07-25  8:03 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=000000000000a33bfc06014b28c9@google.com \
    --to=syzbot+a76d93c00034a9fd23f5@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.