Re: kern/53931: posix_fadvise_reg test case fails randomly on real hardware

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR kern/53931; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: David Holland <dholland-bugs%netbsd.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/53931: posix_fadvise_reg test case fails randomly on real
 hardware
Date: Sun, 3 Feb 2019 00:09:47 +0200

 David Holland wrote:
 >   >   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.
 
 Quite possible.  Thanks for the analysis.
 
 >  Does rump actually have a means for handling these broken syscalls
 >  correctly, and if so, is posix_fadvise tagged appropriately?
 
 I don't know.
 
 >  It is bizarre that the behavior would depend on the nature of the
 >  underlying hardware though.
 
 If it's some kind of race condition, it's hardly surprising if it
 happens on multiprocessor but not on a (software emulation of a)
 uniprocessor.
 -- 
 Andreas Gustafsson, gson%gson.org@localhost