You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
splice07 seems to depend on torvalds/linux@36e2c74 ("fs: don't allow splice read/write without explicit ops") to pass. I've compiled a list of failing combinations on 5.4, but I'm not sure what's the right approach to modifying the test:
in_fd
out_fd
error
TST_FD_PIPE_READ
TST_FD_EPOLL
hangs
TST_FD_PIPE_READ
TST_FD_EVENTFD
hangs
TST_FD_PIPE_READ
TST_FD_SIGNALFD
hangs
TST_FD_PIPE_READ
TST_FD_TIMERFD
hangs
TST_FD_PIPE_READ
TST_FD_PIDFD
hangs
TST_FD_PIPE_READ
TST_FD_PERF_EVENT
hangs
TST_FD_PIPE_READ
TST_FD_IO_URING
hangs
TST_FD_PIPE_READ
TST_FD_BPF_MAP
hangs
TST_FD_PIPE_READ
TST_FD_FSOPEN
hangs
TST_FD_PIPE_READ
TST_FD_FSPICK
hangs
TST_FD_INOTIFY
TST_FD_PIPE_WRITE
hangs
TST_FD_DIR
TST_FD_PIPE_WRITE
EISDIR
TST_FD_PERF_EVENT
TST_FD_PIPE_WRITE
ENODATA
TST_FD_FSOPEN
TST_FD_PIPE_WRITE
ENODATA
TST_FD_FSPICK
TST_FD_PIPE_WRITE
ENODATA
Should it just be gated by kernel version or is there a preferred way to modify it so that it is backwards compatible?
The text was updated successfully, but these errors were encountered:
@metan-ucw@mdoucha know more than me. AFAIK we noticed at least incorrect errno EISDIR (obviously there is also ENODATA) and hang on TST_FD_EPOLL (I did not know about the following hangs), although AFAIK we did not reported it to the kernel mainline ML (lore).
splice07 seems to depend on torvalds/linux@36e2c74 ("fs: don't allow splice read/write without explicit ops") to pass.
The right approach would be to fix the kernel since all these failures are kernel bugs (maybe except for inotify -> writable pipe). It does not make sense to modify the test, not even to add a kernel version check.
splice07 seems to depend on torvalds/linux@36e2c74 ("fs: don't allow splice read/write without explicit ops") to pass. I've compiled a list of failing combinations on 5.4, but I'm not sure what's the right approach to modifying the test:
Should it just be gated by kernel version or is there a preferred way to modify it so that it is backwards compatible?
The text was updated successfully, but these errors were encountered: