Date: Mon, 21 Aug 2017 21:04:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-dtrace@FreeBSD.org Subject: [Bug 219451] [dtrace] Certain llquantize() parameters trigger assertion Message-ID: <bug-219451-32976-Y8gdSrEoq7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219451-32976@https.bugs.freebsd.org/bugzilla/> References: <bug-219451-32976@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219451 --- Comment #2 from Mark Johnston <markj@FreeBSD.org> --- It seems the real issue here is an overflow when computing 100^10? 9 is the largest power of 100 that fits in a 64-bit int. There's a check that's supposed to catch this. Indeed, it does if we change= the upper power from 10 to 11: git (dev/vm-init) markj@wkstn-mjohnston> sudo dtrace -n 'syscall:::return {@[execname] =3D llquantize(arg0, 100, 0, 11, 100);} tick-1s {exit(0);}' dtrace: invalid probe specifier syscall:::return {@[execname] =3D llquantize(arg0, 100, 0, 11, 100);} tick-1s {exit(0);}: llquantize( ) factor (100) raised to power of high magnitude (11) overflows 64-bits --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219451-32976-Y8gdSrEoq7>