mbox series

[0/2] Increase fsync() coverage - GH#452

Message ID 20190917101706.10013-1-mdoucha@suse.cz
Headers show
Series Increase fsync() coverage - GH#452 | expand

Message

Martin Doucha Sept. 17, 2019, 10:17 a.m. UTC 
This patchset partially solves GH issue #452. New test cases: Call fsync()
on open socket, fifo, and closed non-negative file descriptor.

What is not tested (yet): fsync() calls which produce EINTR, EIO, ENOSPC,
EROFS or EDQUOT errors. These errors can only happen while data in kernel
buffers is being written to disk. Producing these errors reliably would
require some control over the block device underlying the file system.

Martin Doucha (2):
  Update syscalls/fsync03 to new API
  Improve coverage in syscalls/fsync03

 testcases/kernel/syscalls/fsync/fsync03.c | 189 +++++++++-------------
 1 file changed, 76 insertions(+), 113 deletions(-)