Date: Tue, 07 Jan 2020 20:10:14 +0000 From: bugzilla-noreply@freebsd.org To: emulation@FreeBSD.org Subject: [Bug 243155] Linuxulator: broken fadvise64 for 32-bit applications on amd64 Message-ID: <bug-243155-4077-PefNMszkwr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243155-4077@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243155 --- Comment #2 from Alex S <iwtcex@gmail.com> --- (In reply to Mark Johnston from comment #1) > Are you sure that this isn't just a truss bug? Let's adjust the test a bit: % cat fadvice_bug.c #define _GNU_SOURCE #include <assert.h> #include <fcntl.h> int main() { int fd = open("/etc/passwd", O_RDONLY); assert(fd > 0); posix_fadvise(fd, 0, 0, -1); return 0; } % /compat/linux/bin/gcc -m64 fadvice_bug.c -o fadvice_bug64 % truss ./fadvice_bug64 ... linux_fadvise64(0x3,0x0,0x0,0xffffffffffffffff) ERR#-22 'Invalid argument' ... % /compat/linux/bin/gcc -m32 fadvice_bug.c -o fadvice_bug32 % truss ./fadvice_bug32 ... linux_fadvise64(0x3,0x0,0x0,0x0) = 0 (0x0) ... > amd64's 32-bit Linux syscall definition for fadvise64 looks right. That's the weird part. It looks right to me as well, at least at first sight. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243155-4077-PefNMszkwr>