copy_file_range changed behavior on 5.3, which would cause such failures.
LTP changes to accomodate that were committed on September 30th and October 29th, though.
Maybe this could be caused by the combination of linux 5.3, glibc 2.27 and whatever ltp version was used. Do we track the ltp commit id that was tested somehow?
copy_file_range changed behavior on 5.3, which would cause such failures.
LTP changes to accomodate that were committed on September 30th and October 29th, though.
Maybe this could be caused by the combination of linux 5.3, glibc 2.27 and whatever ltp version was used. Do we track the ltp commit id that was tested somehow?
Cascardo.