[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/53931: posix_fadvise_reg test case fails randomly on real hardware
The following reply was made to PR kern/53931; it has been noted by GNATS.
From: David Holland <dholland-bugs%netbsd.org@localhost>
Subject: Re: kern/53931: posix_fadvise_reg test case fails randomly on real
Date: Sat, 2 Feb 2019 18:45:56 +0000
On Fri, Feb 01, 2019 at 03:30:00PM +0000, Andreas Gustafsson wrote:
> The posix_fadvise_reg test case of the lib/libc/sys/t_posix_fadvise
> test program is failing randomly on real amd64 hardware, with six
> failures in the last 30 runs on my bare metal testbed. It fails
> with the message
> t_posix_fadvise.c:135: errno != 999: got: Operation already in progress
The system call cannot generate EINPROGRESS, and furthermore, the
system call does not touch errno (it is one of the broken POSIX
innovations that returns an errno value instead) so something in the
rump plumbing must be doing it.
Does rump actually have a means for handling these broken syscalls
correctly, and if so, is posix_fadvise tagged appropriately?
It is bizarre that the behavior would depend on the nature of the
underlying hardware though.
David A. Holland
Main Index |
Thread Index |