aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
7 daysAndroid.bp: fix build complaint of missing lapi/syscalls/orderHEADmastermainEdward Liaw
Fixes this build complaint: cat: ./tools/src/external/ltp/include/lapi/syscalls/order: No such file or directory Bug: 327505050 Test: mma Change-Id: Idf37c18449a2fa200dd755e6149f709b0ac7618b Signed-off-by: Edward Liaw <edliaw@google.com>
10 dayscontrollers: remove use of LINE_MAXEdward Liaw via ltp
LINE_MAX is not defined in Android's bionic and seems to be a leftover of POSIX standards. In this case, replace the use of fgets with getline, which will resize the line buffer if needed. Also, drop some unnecessarily exported variables. Bug: 333536295 Test: atest vts_ltp_test_x86_64 Change-Id: Iacb556b201530c49f3509bb4b35df39c35a0f57d Signed-off-by: Edward Liaw <edliaw@google.com> Reviewed-by: Cyril Hrubis <chrubis@suse.cz> (cherry picked from commit 70d3ea085665c8f11bda58a0645578d06d894ab3)
10 daysMerge "bionic-compat.h: no need to define LINE_MAX any more." into mainEdward Liaw
13 daysRemove joefradley@google.com from OWNERSOwner Cleanup Bot
This suggested change is automatically generated based on group memberships and affiliations. If this change is unnecessary or in error, vote CR -1 and the bot will abandon it. Vote CR +1/2 to approve this change. See the owner's recent activity for context: https://android-review.googlesource.com/q/joefradley@google.com To report an issue, file a bug in the Infra>Codereview component. Change-Id: I90c3a9efed229dcddace45a67610c8de49172fd1
2024-04-18Merge "Convert ltp from Android.mk to Android.bp" into mainTreehugger Robot
2024-04-17bionic-compat.h: no need to define LINE_MAX any more.Elliott Hughes
We've added this bad idea to bionic for source compatibility with existing code, and we've also removed ltp's uses of this macro upstream. Change-Id: I84b78eee8a87a3250c846b7868ded7c0c5d98ffb
2024-04-16Convert ltp from Android.mk to Android.bpyangbill
This CL is doing the following: - Remove Android.mk and android/Android.mk - Update auto_build_generator to generate related Android.bp file - Create android/Android.bp generate by auto_build_generator to replace android/Android.mk - Create testcases/Android.bp generate by auto_build_generator which is the replacement of external/ltp/android/Android.ltp.mk - Update external/ltp/Android.bp to export runtest related artifacts for ltp test Bug: 330289736 Bug: 330452940 Test: m ltp Test: diff the output tree before and after the patch '$ m clean ; m ltp' tree out/target/product/vsoc_x86_64/testcases/ > new.txt tree out_ltp/target/product/vsoc_x86_64/testcases/ > old.txt diff new.txt old.txt tree out/target/product/vsoc_x86_64/data/nativetest64/ > new_native_tests_64.txt tree out_ltp/target/product/vsoc_x86_64/data/nativetest64/ > old_native_tests_64.txt diff new_native_tests_64.txt old_native_tests_64.txt tree out/target/product/vsoc_x86_64/data/nativetest/ > new_native_tests_32.txt tree out_ltp/target/product/vsoc_x86_64/data/nativetest/ > old_native_tests_32.txt diff new_native_tests_32.txt old_native_tests_32.txt Change-Id: Ibeb16e69da21931a111265258f8d0901263870e3
2024-04-15bionic-compat.h: remove more unused definitions.Elliott Hughes
Upstream ltp has cleaned up since these were last needed. Change-Id: I091e4e2345181a883c5b6ade40901dc1b33cab9d
2024-04-09bionic-compat.h: more cleanup.Elliott Hughes
One macro that wasn't provided by bionic now is, and another macro no longer assumes a 4KiB page size in bionic and so doesn't need to be redefined here. Also remove an unnecessary #include. Change-Id: If47eaa94c52d34cdb068042aecc8fccd6ef5e94b
2024-04-09bionic-compat.h: remove obsolete cruft.Elliott Hughes
These things either _are_ in bionic, or have been cleaned up in ltp. Change-Id: I684a316ff323a6a2ffb280b3fa0edf4d6d24ecd5
2024-04-02[automerger skipped] Merge changes from topic "ltp-20230929-android14-tests" ↵Treehugger Robot
into android14-tests-dev am: cdb9cd95d8 -s ours am skip reason: Merged-In I11e47073bcdafda0a847ddf95bb52a889f498c6b with SHA-1 22ab8b7c2f is already in history Original change: https://android-review.googlesource.com/c/platform/external/ltp/+/2908777 Change-Id: Ib781249e4566fbc250a67bfa3757b5ca6d59427c Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2024-04-02[automerger skipped] cgroup: Fix scanning V1 mount options am: 74f79dc224 -s ↵Richard Palethorpe
ours am skip reason: Merged-In I11e47073bcdafda0a847ddf95bb52a889f498c6b with SHA-1 22ab8b7c2f is already in history Original change: https://android-review.googlesource.com/c/platform/external/ltp/+/2908777 Change-Id: I61c29464f5cb6d48ef308455592f5f668babf774 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2024-04-02Merge changes from topic "ltp-20230929-android14-tests" into android14-tests-devandroid14-tests-devTreehugger Robot
* changes: cgroup: Fix scanning V1 mount options cgroup: Handle trailing new line in cgroup.controllers compare_ltp_projects.py: Fix test sorting, adjust printing madvise11: Allow test to skip if MADV_SOFT_OFFLINE is not supported madvise11: Replace /etc/mtab with /proc/mounts syscalls/process_madvise01: fix smaps scan and min_swap_avail tst_clocks.c: Fix stack smashing on 32bit tst_kvercmp: Handle larger kernel version numbers getpgid01: On Android, pgid(1) is 0 instead of 1 pipe07: refactor exp_num_pipes pipe07: close /proc/self/fd after counting fds config.h: Compile with linux/ioprio.h to fix ioprio_set03 sched.h: Don't exclude clone_args_minimal when HAVE_STRUCT_CLONE_ARGS is set ltp-version.h: Generate with genrule mq_notify03: disable test because don't have mqueue kvm: Disable kvm tests make_parser.py: Handle as (gnu assembler) command in makefile android_build_generator.py: Print more info when failing with compile target LTP 20230929 Merge tag '20230929'
2024-03-28input_helper: Modify the check range of the input event number am: 26a125c969akihisa.kogure.ke
Original change: https://android-review.googlesource.com/c/platform/external/ltp/+/3009116 Change-Id: Iaadd408001f0115ce752ef975d083fba533c26f0 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2024-03-27input_helper: Modify the check range of the input event numberakihisa.kogure.ke
If the input event number is greater than 32, the newly added event ID will be 256 or later. When there were already 32 input events in the device, this test program only checked 0~99, so it failed because it could not find a new input event ID. In order to eliminate this failure, we changed the event ID range to be checked by this test program to 0~1023. (https://github.com/torvalds/linux/commit/7f8d4cad1e4e11a45d02bd6e024cc2812963c38a, it looks like the upper limit should be 1023.) Bug: 330269984 Test: ltp Change-Id: I1b53008b15641fcdccf214af9183de1c29a3309c
2024-03-27input_helper: Modify the check range of the input event numberakihisa.kogure.ke
If the input event number is greater than 32, the newly added event ID will be 256 or later. When there were already 32 input events in the device, this test program only checked 0~99, so it failed because it could not find a new input event ID. In order to eliminate this failure, we changed the event ID range to be checked by this test program to 0~1023. (https://github.com/torvalds/linux/commit/7f8d4cad1e4e11a45d02bd6e024cc2812963c38a, it looks like the upper limit should be 1023.) Bug: 330269984 Test: ltp Change-Id: I1b53008b15641fcdccf214af9183de1c29a3309c
2024-02-29tst_fd: Use raw syscall for fanotify_init() am: 90164cf586Edward Liaw
Original change: https://android-review.googlesource.com/c/platform/external/ltp/+/2983200 Change-Id: Id5fc92abaa56664122b899bcee30ecfefe12ce99 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2024-02-29nft02: Fix initializer element is not a compile-time constant am: 54cba33603Edward Liaw
Original change: https://android-review.googlesource.com/c/platform/external/ltp/+/2983199 Change-Id: I28e601be8f18a435661040297b712920f2196954 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2024-02-29LTP 20240129 am: a8ba9c7451Edward Liaw
Original change: https://android-review.googlesource.com/c/platform/external/ltp/+/2983198 Change-Id: I62de3c640f3d684959352b06549f71d95289c897 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2024-02-29Merge tag '20240129' am: 1470d30613Edward Liaw
Original change: https://android-review.googlesource.com/c/platform/external/ltp/+/2983197 Change-Id: I0100ddfad10fd2864e7e0d5c9b3d07e371f1998a Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
2024-02-29tst_fd: Use raw syscall for fanotify_init()Edward Liaw
Some systems do not provide sys/fanotify.h, such as Android. We can use the raw syscall for open_fanotify to avoid importing the header file. Bug: 327505050 Test: mma Link: https://lore.kernel.org/ltp/20240223000543.1135129-1-edliaw@google.com/ Fixes: https://github.com/linux-test-project/ltp/issues/1134 Suggested-by: Cyril Hrubis <chrubis@suse.cz> Reviewed-by: Li Wang <liwang@redhat.com> Reviewed-by: Petr Vorel <pvorel@suse.cz> Change-Id: I47aaaa4846a360be62059d140dbda00964966a4d Signed-off-by: Edward Liaw <edliaw@google.com> (cherry picked from commit 7b1c5e0a239e1204ea444315e0b9c256ddbfd380)
2024-02-29nft02: Fix initializer element is not a compile-time constantEdward Liaw
Replace strlen + 1 with sizeof so that struct will evaluate as static const. Bug: 327505050 Test: mma Change-Id: I18d0a8e46ec5116e924e1501e889a7efa502583e Signed-off-by: Edward Liaw <edliaw@google.com>
2024-02-29LTP 20240129Edward Liaw
****************** Tests Suites ****************** Added (0) Deleted (2) connectors fsx ********************* Tests ********************** Added (36) Deleted (53) cve.cve-2023-0461 crashme.fork12 cve.cve-2023-31248 ltp-aiodio.part3.FSX032 kernel_misc.cn_pec_sh ltp-aiodio.part3.FSX033 ltp-aiodio.part3.fsx01 ltp-aiodio.part3.FSX034 ltp-aiodio.part3.fsx02 ltp-aiodio.part3.FSX035 ltp-aiodio.part3.fsx03 ltp-aiodio.part3.FSX036 ltp-aiodio.part3.fsx04 ltp-aiodio.part3.FSX037 ltp-aiodio.part3.fsx05 ltp-aiodio.part3.FSX038 ltp-aiodio.part3.fsx06 ltp-aiodio.part3.FSX039 ltp-aiodio.part3.fsx07 ltp-aiodio.part3.FSX040 ltp-aiodio.part3.fsx08 ltp-aiodio.part3.FSX041 ltp-aiodio.part3.fsx09 ltp-aiodio.part3.FSX042 ltp-aiodio.part3.fsx10 ltp-aiodio.part3.FSX043 ltp-aiodio.part3.fsx12 ltp-aiodio.part3.FSX044 ltp-aiodio.part3.fsx13 ltp-aiodio.part3.FSX045 ltp-aiodio.part3.fsx14 ltp-aiodio.part3.FSX046 ltp-aiodio.part3.fsx15 ltp-aiodio.part3.FSX047 ltp-aiodio.part3.fsx16 ltp-aiodio.part3.FSX048 ltp-aiodio.part3.fsx17 ltp-aiodio.part3.FSX049 ltp-aiodio.part3.fsx18 ltp-aiodio.part3.FSX050 ltp-aiodio.part3.fsx19 ltp-aiodio.part3.FSX051 ltp-aiodio.part3.fsx20 ltp-aiodio.part3.FSX052 ltp-aiodio.part3.fsx21 ltp-aiodio.part3.FSX053 ltp-aiodio.part3.fsx22 ltp-aiodio.part3.FSX054 mm.ksm07 ltp-aiodio.part3.FSX055 sched.proc_sched_rt01 ltp-aiodio.part3.FSX056 syscalls.accept03 ltp-aiodio.part3.FSX057 syscalls.fchmodat02 ltp-aiodio.part3.FSX058 syscalls.gettid02 ltp-aiodio.part3.FSX059 syscalls.pathconf02 ltp-aiodio.part3.FSX060 syscalls.pipe15 ltp-aiodio.part3.FSX061 syscalls.ptrace06 ltp-aiodio.part3.FSX062 syscalls.sched_setscheduler04 ltp-aiodio.part3.FSX063 syscalls.setsockopt10 ltp-aiodio.part3.FSX064 syscalls.splice06 ltp-aiodio.part3.FSX065 syscalls.splice07 ltp-aiodio.part3.FSX066 ltp-aiodio.part3.FSX067 ltp-aiodio.part3.FSX068 ltp-aiodio.part3.FSX069 ltp-aiodio.part3.FSX070 ltp-aiodio.part3.FSX071 ltp-aiodio.part3.FSX072 ltp-aiodio.part3.FSX073 ltp-aiodio.part3.FSX074 ltp-aiodio.part3.FSX075 ltp-aiodio.part3.FSX076 ltp-aiodio.part3.FSX077 ltp-aiodio.part3.FSX078 ltp-aiodio.part3.FSX079 syscalls.getdtablesize01 syscalls.link03 syscalls.symlink05 syscalls.timerfd03 Bug: 327505050 Test: N/A Change-Id: Iae910d5d96b1299dc8d7c9b9765f8b32fd6a829f Signed-off-by: Edward Liaw <edliaw@google.com>
2024-02-29Merge tag '20240129'Edward Liaw
Update LTP to 20240129 release. Bug: 327505050 Test: N/A Change-Id: I119e0b87d1c07c98fe6e4f63c6afd8ba01ff8372 Signed-off-by: Edward Liaw <edliaw@google.com>
2024-01-29LTP 20240129Petr Vorel
Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-29isofs.sh: Test genisoimage, xorriso and mksisofsSubramanya Swamy
Run test an all 3 tools: genisoimage, xorriso and mksisofs. mkisofs, genisoimage and xorriso tools are present as separate tools in some distros while in others they are symlinks to one another. Tests are skipped on symlinks. mkisofs supports only -hfs option genisoimage supports both -hfs and -hfsplus options xorrisofs supports only -hfsplus option This actually fixes xorrisofs on CentOS which is a symlink to mkisofs and because it does not supports -hfs test IMHO fails. Link: https://lore.kernel.org/ltp/20240129092232.599010-1-pvorel@suse.cz/ Co-Authored-By: Petr Vorel <pvorel@suse.cz> Reviewed-by: Petr Vorel <pvorel@suse.cz> Reviewed-by: Cyril Hrubis <chrubis@suse.cz> Signed-off-by: Subramanya Swamy <subramanya.swamy.linux@gmail.com> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-29splice07: Whitelist /proc/self/maps on pipe writeMartin Doucha
Just like with /dev/zero, splicing /proc/self/maps to writable pipe is expected to pass. After generic splice() read emulation was removed, it was reimplemented in commit b0072734ffaa ("tty, proc, kernfs, random: Use copy_splice_read()") Link: https://lore.kernel.org/ltp/20240129104327.10639-1-mdoucha@suse.cz/ Reviewed-by: Petr Vorel <pvorel@suse.cz> Reviewed-by: Cyril Hrubis <chrubis@suse.cz> Signed-off-by: Martin Doucha <mdoucha@suse.cz>
2024-01-29splice07: Whitelist /dev/zero on pipe writePetr Vorel
/dev/zero on pipe write started to succeeded on kernel 6.7 due commit 1b057bd800c3 ("drivers/char/mem: implement splice() for /dev/zero, /dev/full"). This is just a quick fix before upcoming LTP release, we should write a separate test to test 1b057bd800c3 after the release Link: https://lore.kernel.org/ltp/20240125155107.430656-1-pvorel@suse.cz/ Reviewed-by: Martin Doucha <mdoucha@suse.cz> Reviewed-by: Cyril Hrubis <chrubis@suse.cz> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-29syscalls/pwritev: Make make check happyXiao Yang
1) Relicense to GPL v2+ for pwritev.h. 2) Add LTP Copyright. Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com> Reviewed-by: Petr Vorel <pvorel@suse.cz>
2024-01-29syscalls/pwritev: Fix docparseXiao Yang
Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com> Reviewed-by: Petr Vorel <pvorel@suse.cz>
2024-01-29syscalls/preadv: Make make check happyXiao Yang
1) Relicense to GPL v2+ for preadv.h. 2) Add LTP Copyright. Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com> Reviewed-by: Petr Vorel <pvorel@suse.cz>
2024-01-29syscalls/preadv: Fix docparseXiao Yang
Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com> Reviewed-by: Petr Vorel <pvorel@suse.cz>
2024-01-27lapi/io_uring: <sys/types.h> => <linux/types.h>Petr Vorel
This fixes compilation on old toolchains: Some old toolchains require to add <linux/types.h> to missing kernel types: tst_safe_io_uring.c: In function ‘safe_io_uring_init’: tst_safe_io_uring.c:34:45: error: ‘__u32’ undeclared (first use in this function) 34 | params->sq_entries * sizeof(__u32); | ^~~~~ io_uring02.c: In function ‘drain_fallback’: io_uring02.c:106:34: error: ‘__u64’ undeclared (first use in this function) 106 | sqe_ptr->addr = (__u64)&spam_header; | ^~~~~ io_uring02.c:106:34: note: each undeclared identifier is reported only once for each function it appears in io_uring02.c: In function ‘run’: io_uring02.c:221:26: error: ‘__u64’ undeclared (first use in this function) 221 | sqe_ptr->addr = (__u64)&beef_header; | ^~~~~ Newer kernel headers includes <linux/types.h> in <linux/io_uring.h>, but we still support compilers without this header. Therefore replace <sys/types.h> in lapi header with <linux/types.h>. Link: https://lore.kernel.org/ltp/20240126111506.491324-1-pvorel@suse.cz/ Fixes: 3f2ff5431 ("Add safe functions for io_uring to LTP library") Fixes: c4f669f13 ("Add test for CVE 2020-29373") Reviewed-by: Cyril Hrubis <chrubis@suse.cz> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-25fanotify{01,09,10}: Check for report fid support with mount markAmir Goldstein
There are now filesystems other than overlayfs (e.g. fuse) that do not support filesystem and mount marks with FAN_REPORT_FID. Adapt tests to runs correctly on those filesystems (tested with ntfs-3g). Link: https://lore.kernel.org/ltp/CAOQ4uxjMiPG5E5=jirxT_D=NDxdUfA2Vp8u1yNZ=YH_SxC0S8Q@mail.gmail.com/ Reviewed-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
2024-01-25fallocate06: Increase test loop device size to 1GBMartin Doucha
Btrfs on newer kernels may have issues with running out of space for metadata in the fill FS+CoW subtest if the test device is too small. Increase minimal device size to avoid the corner case. Signed-off-by: Martin Doucha <mdoucha@suse.cz> Reviewed-by: Petr Vorel <pvorel@suse.cz> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
2024-01-25fs_fill: Increase timeout to 5 minPetr Vorel
1 min timeout sometimes is not enough. Although it could be fixed LTP_RUNTIME_MUL=2, let's prolong the default timeout. Link: https://lore.kernel.org/ltp/20240125100009.387096-1-pvorel@suse.cz/ Fixes: 848dd6fba ("fs_fill: Increase test loop device size to 1GB") Reviewed-by: Cyril Hrubis <chrubis@suse.cz> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-25fs_fill: Increase test loop device size to 1GBWei Gao via ltp
On PPC64 the page size is 64K and this causes trouble on btrfs filesystems of small size (LTP currently uses 300M), the threads could compete for a very small number of pages/blocks to actually write the data. So increase minimal device size to 1G avoid the corner case. Link: https://lore.kernel.org/ltp/20240125004732.9549-1-wegao@suse.com/ Reviewed-by: Petr Vorel <pvorel@suse.cz> Reviewed-by: Martin Doucha <mdoucha@suse.cz> Signed-off-by: Wei Gao <wegao@suse.com>
2024-01-25mmap04.c: Avoid vma mergingAvinesh Kumar
We hit a scenario where new mapping was merged with existing mapping of same permission and the return address from the mmap was hidden in the merged mapping in /proc/self/maps, causing the test to fail. To avoid this, we first create a 2-page mapping with the different permissions, and then remap the 2nd page with the perms being tested. Link: https://lore.kernel.org/ltp/20240124132603.16199-1-akumar@suse.de/ Reported-by: Martin Doucha <mdoucha@suse.cz> Reviewed-by: Martin Doucha <mdoucha@suse.cz> Reviewed-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: Avinesh Kumar <akumar@suse.de>
2024-01-24fanotify16: Fix test failure on FUSEAmir Goldstein
Split SAFE_CREAT() into explicit SAFE_MKNOD() and SAFE_OPEN(), because with atomic open (e.g. fuse), SAFE_CREAT() generates FAN_OPEN before FAN_CREATE (tested with ntfs-3g), which is inconsistent with the order of events expectated from other filesystems. Reviewed-by: Petr Vorel <pvorel@suse.cz> Tested-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
2024-01-24fanotify{14,15,16}: Check for filesystem mark support on filesystemAmir Goldstein
There are now filesystems other than overlayfs (e.g. fuse) that do not support filesystem and mount marks with FAN_REPORT_FID. Adapt tests to runs correctly on those filesystems (tested with ntfs-3g). Reviewed-by: Petr Vorel <pvorel@suse.cz> Reviewed-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
2024-01-24fanotify13: Use generic check for mark type support on filesystemAmir Goldstein
This test has a specific check for AT_HANDLE_FID file handles, which is a specific reason for a filesystem (e.g. overlayfs) not supporting filesystem and mount marks with FAN_REPORT_FID. We now have a generic check for mark type support on filesystem, so use the more generic check instead of the specific AT_HANDLE_FID check, do decide if test case needs to be run. There are now filesystems other than overlayfs (e.g. fuse) that do not support filesystem and mount marks with FAN_REPORT_FID, so this test now runs correctly on those filesystems as well (tested with ntfs-3g). Reviewed-by: Petr Vorel <pvorel@suse.cz> Reviewed-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
2024-01-24network: Fix tst_brk TFAILPetr Vorel
It needs to be replaced with tst_res TFAIL and return Link: https://lore.kernel.org/ltp/20240123162647.210424-5-pvorel@suse.cz/ Fixes: 1878502f6 ("tst_test.sh/tst_brk(): Allow only TBROK and TCONF") Reviewed-by: Li Wang <liwang@redhat.com> Reviewed-by: Martin Doucha <mdoucha@suse.cz> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-24kernel: Fix tst_brk TFAILPetr Vorel
It needs to be replaced with tst_res TFAIL and return Link: https://lore.kernel.org/ltp/20240123162647.210424-4-pvorel@suse.cz/ Fixes: 1878502f6 ("tst_test.sh/tst_brk(): Allow only TBROK and TCONF") Reviewed-by: Li Wang <liwang@redhat.com> Reviewed-by: Cyril Hrubis <chrubis@suse.cz> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-24commands: Fix tst_brk TFAILPetr Vorel
It needs to be replaced with tst_res TFAIL and return Link: https://lore.kernel.org/ltp/20240123162647.210424-3-pvorel@suse.cz/ Fixes: 1878502f6 ("tst_test.sh/tst_brk(): Allow only TBROK and TCONF") Reviewed-by: Li Wang <liwang@redhat.com> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-24tst_test.sh: Improve info on wrong tst_brk paramPetr Vorel
Print wrong $res parameter in tst_brk helps searching wrong code. Link: https://lore.kernel.org/ltp/20240123162647.210424-2-pvorel@suse.cz/ Reviewed-by: Li Wang <liwang@redhat.com> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-24lib: tst_fd: Use tst_res(TCONF)Petr Vorel
to avoid error on older distro (kernel 4.12) tst_fd.c:144: TBROK: pidfd_open(): ENOSYS (38) We need tst_res() so that tst_fd_next() iterator continues with next file descriptor and TCONF. Fixes: a2b945776 ("lib: tst_fd: Avoid tst_brk(TCONF, ...) on older distros") Suggested-by: Cyril Hrubis <chrubis@suse.cz> Reviewed-by: Cyril Hrubis <chrubis@suse.cz> Reviewed-by: Martin Doucha <mdoucha@suse.cz> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-24lib: tst_fd: Avoid tst_brk(TCONF, ...) on older distrosCyril Hrubis
All the lapi/ functions does call tst_syscall() that does tst_brk(TCONF, ...) on ENOSYS which exits the testrun prematurely on older distributions. Signed-off-by: Cyril Hrubis <chrubis@suse.cz> Reported-by: Martin Doucha <mdoucha@suse.cz> Reviewed-by: Martin Doucha <mdoucha@suse.cz> Reviewed-by: Petr Vorel <pvorel@suse.cz>
2024-01-24virt_lib.sh: Fix device name in error messagePetr Vorel
Suggested-by: Martin Doucha <mdoucha@suse.cz> Signed-off-by: Petr Vorel <pvorel@suse.cz>
2024-01-24Increase .max_runtime for fsx-linuxAndrea Cervesato
Sometimes fsx-linux test is timing out on slow systems. We increase its value to 1800 seconds, so we ensure test won't timeout in most cases. The value has been choosen according with aio testing suite, which has 1800 seconds timeout and it worked really well so far. Fixes: 176667f40710 ("fsx-linux: Add .max_runtime = 60") Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
2024-01-22keyctl05: Improve the dns_res_payload for boundary testingPengfei Xu
kernel commit acc657692aed ("keys, dns: Fix size check of V1 server-list header") from upcoming v6.8-rc1 (going to be backported to stable), which fixes the add_key syscall incoming data boundary size issue, 6 bytes incoming data is now enough. Link: https://lore.kernel.org/ltp/20240111100636.1897637-1-pvorel@suse.cz/ Reviewed-by: Petr Vorel <pvorel@suse.cz> Signed-off-by: Pengfei Xu <pengfei.xu@intel.com> [ pvorel: add acc657692aed, reword commit message ] Signed-off-by: Petr Vorel <pvorel@suse.cz>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-02 14:37:17 +0000