Re: Suspicious xfstest failures to ksmbd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2022년 5월 29일 (일) 오전 7:38, Steve French <smfrench@xxxxxxxxx>님이 작성:
>
> Noticed a few differences between ksmbd test results and other servers
> that may be server bugs:
> generic/615 22s ... - output mismatch (see
> /home/smfrench/xfstests-dev/results//generic/615.out.bad)
>     --- tests/generic/615.out   2022-01-30 15:05:53.495186894 -0600
>     +++ /home/smfrench/xfstests-dev/results//generic/615.out.bad
>  2022-05-28 16:29:12.603177975 -0500
>     @@ -1,3 +1,4 @@
>      QA output created by 615
>      Testing buffered writes
>     +error: stat(2) reported zero blocks
>      Testing direct IO writes
>     ...
>     (Run 'diff -u /home/smfrench/xfstests-dev/tests/generic/615.out
> /home/smfrench/xfstests-dev/results//generic/615.out.bad'  to see the
> entire diff)
>
> also test 208 fails:
> generic/208 201s ... [failed, exit status 1]- output mismatch (see
> /home/smfrench/xfstests-dev/results//generic/208.out.bad)
>     --- tests/generic/208.out   2020-01-24 17:11:18.720859829 -0600
>     +++ /home/smfrench/xfstests-dev/results//generic/208.out.bad
>  2022-05-27 21:43:43.204933555 -0500
>     @@ -1,2 +1,2 @@
>      QA output created by 208
>     -ran for 200 seconds without error, passing
>     +buffered write returned 12582912
>     \ No newline at end of file
>
> Tests generic/472, generic/497 and generic/554 (swapfile tests) are
> skipped to ksmbd (with "swapfile not supported") but not to Samba
>

The patch, "ksmbd: remove unnecessary generic_fillattr in smb2_open"
fixes generic/472 and generic/497. But in the kernel 5.19 or later,
These still are skipped for ksmbd and Samba. Because swap_rw, a new
address_space operation is not implemented in cifs.

>
> Also would be interesting to see why test generic/586 fails (although
> this fails to multiple servers, could be client bug):
> generic/586 11s ... - output mismatch (see
> /home/smfrench/xfstests-dev/results//generic/586.out.bad)
>     --- tests/generic/586.out   2020-06-14 15:13:59.924160846 -0500
>     +++ /home/smfrench/xfstests-dev/results//generic/586.out.bad
>  2022-05-28 16:28:54.723201574 -0500
>     @@ -1,2 +1,101 @@
>      QA output created by 586
>     +[0]: sbuf.st_size=1048576, expected 2097152.
>     +[1]: sbuf.st_size=1048576, expected 2097152.
>
>
> Test 213 should also correctly return no space on disk (could be client bug)
> generic/213 0s ... - output mismatch (see
> /home/smfrench/xfstests-dev/results//generic/213.out.bad)
>     --- tests/generic/213.out   2020-01-24 17:11:18.720859829 -0600
>     +++ /home/smfrench/xfstests-dev/results//generic/213.out.bad
>  2022-05-27 18:50:38.984025733 -0500
>     @@ -1,4 +1,3 @@
>      QA output created by 213
>      We should get: fallocate: No space left on device
>      Strangely, xfs_io sometimes says "Success" when something went wrong, FYI
>     -fallocate: No space left on device
>
>
> -
>
> --
> Thanks,
>
> Steve



-- 
Thanks,
Hyunchul




[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux