syscalls/unlinkat01: Bugfix and update to new API
PATCH 1/1 syscalls/unlinkat01: Bugfix and update to new API
Hi Petr,
Thanks for your review!
Quoted 13 lines
Review static const int flags[] = { 0, 0, 0, 0, 9999, 0, · line 41
Quoted 8 lines
(quoted diff) +0
-3-char *TCID = "unlinkat01"; -int TST_TOTAL = TEST_CASES; - static const char pathname[] = "unlinkattestdir", subpathname[] = "unlinkatsubtestdir", subpathdir[] = "unlinkattestdir/unlinkatsubtestdir",@@ -65,82 +41,79 @@ static const int flags[] = { 0, 0, 0, 0, 9999, 0, AT_REMOVEDIR };Could you please use static struct for testcases data which is the usual way in LTP instead of using arrays? (e.g. in
testcases/kernel/syscalls/access/access02.c).
It helps to the readability of the code as we'll be able to remove lines like:
Quoted 5 lines
fds[1] = fds[4] = fds[6] = fds[0];and most of the setup.
Than you can then drop also
TEST_CASES.
It is more clearer that using arrays, but in this case, fds and filenames can not be complete initialized at first, so it seems there are some trouble to cleanup,
Chould you give me some suggestions for it?
Thanks so much!
Best Regards,
Gongyi
Quoted 162 lines
Hi Zhao,
Quoted 1 line
1) When run the test with option "-i 2", test will fail, and fixed
Good catch!
Quoted 1 line
2) Update to new API
Great! Yes it's working, but it deserves more improvements.
...
Quoted 2 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +0
-0...
Quoted 3 lines
- * Author
- * Yi Yang <[email protected]>
+ * AUTHOR: Yi Yang <[email protected]>nit: * Author: Yi Yang <[email protected]>
testcases/kernel/syscalls/unlinkat/unlinkat01.c
Quoted 6 lines
+ */
testcases/kernel/syscalls/unlinkat/unlinkat01.c +5
-0+ +/*\ +* [Description] +* This test case will verify basic function of unlinkat +* added by kernel 2.6.16 or up. nit: * Basic
unlinkat()tests.Quoted 3 lines
*/
#define
_GNU_SOURCEIMHO you can remove this one.
testcases/kernel/syscalls/unlinkat/unlinkat01.c
Quoted 12 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +1
-10-#include <sys/types.h> -#include <sys/stat.h> -#include <sys/time.h> -#include <fcntl.h> -#include <stdlib.h> -#include <errno.h> -#include <string.h> -#include <signal.h> -#include "test.h" -#include "safe_macros.h" +#include <linux/limits.h> Why this kernel header? I guess for
PATH_MAX, but for that please use <limits.h> (We try to avoid using kernel headers for basic things not related to testing. There is also glibc vs. kernel header clash:
https://sourceware.org/glibc/wiki/Synchronizing_Headers)testcases/kernel/syscalls/unlinkat/unlinkat01.c line 28
Quoted 12 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +3
-0+#include "tst_test.h" #include "lapi/syscalls.h" +#include "tst_safe_stdio.h" #define TEST_CASES 7 +#ifndef AT_FDCWD #define AT_FDCWD -100#endif @@ -45,12 +27,6 @@#define AT_REMOVEDIR 0x200#endif
AT_FDCWDandAT_REMOVEDIRhas been added to <fcntl.h> 10+ years ago, we could safely remove it. But we have them inlapi/fcntl.h, let's use this header please.testcases/kernel/syscalls/unlinkat/unlinkat01.c static const int flags[] = { 0, 0, 0, 0, 9999, 0, · line 41
Quoted 11 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +0
-6-void setup (); -void cleanup (); - -char *TCID ="unlinkat01" ; -int TST_TOTAL =TEST_CASES ; -static const char pathname[] ="unlinkattestdir" , subpathname[] ="unlinkatsubtestdir" , subpathdir[] = "unlinkattestdir/unlinkatsubtestdir",@@ -65,82 +41,79 @@ static const int flags[] = { 0, 0, 0, 0, 9999, 0, AT_REMOVEDIR };Could you please use static struct for testcases data which is the usual way in LTP instead of using arrays? (e.g. in
testcases/kernel/syscalls/access/access02.c).
It helps to the readability of the code as we'll be able to remove lines like:fds[1] = fds[4] = fds[6] = fds[0];and most of the setup.
Than you can then drop also
TEST_CASES.testcases/kernel/syscalls/unlinkat/unlinkat01.c static const int flags[] = { 0, 0, 0, 0, 9999, 0, · line 44
Quoted 4 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +1
-1int myunlinkat (int dirfd,const char *filename,int flags) { -return ltp_syscall (__NR_unlinkat, dirfd, filename, flags); +return tst_syscall (__NR_unlinkat, dirfd, filename, flags); }Could you please use
unlinkat()libc implementation? It was added to glibc in 2.4, musl has it also for 10+ years. Or you can use both raw syscall and libc variant via .test_variants (not needed, we added more variants for some tests, but most of syscall tests does not cover it).testcases/kernel/syscalls/unlinkat/unlinkat01.c static const int flags[] = { 0, 0, 0, 0, 9999, 0, · line 45
Quoted 2 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +1
-1-int main (int ac,char **av) +static void run (int i)i needs to be unsigned int. Compiler warned you (it's good to pay attention to the warnings and don't introduce new ones).
Quoted 48 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +23
-24{ -int lc; -int i; - -if ((tst_kvercmp (2 ,6 ,16 )) <0 ) -tst_brkm (TCONF ,NULL ,"Test must be run with kernel 2.6.16+" ); - -tst_parse_opts (ac, av,NULL ,NULL ); - -setup (); - -for (lc =0 ;TEST_LOOPING (lc); lc++) { - tst_count =0 ; - -for (i =0 ; i <TST_TOTAL ; i++) { -TEST (myunlinkat (fds[i], filenames[i], flags[i])); - -if (TEST_ERRNO == expected_errno[i]) { -tst_resm (TPASS |TTERRNO , -"unlinkat() returned expected errno" ); - }else { -tst_resm (TFAIL |TTERRNO ,"unlinkat() failed" ); - } - } - +if (!expected_errno[i]) { + fds[0 ] =SAFE_OPEN (pathname,O_DIRECTORY ); + fds[1 ] = fds[4 ] = fds[6 ] = fds[0 ]; + +/* tesfile2 will be unlinked by test0. */ +if (access (testfile2,F_OK )) +SAFE_FILE_PRINTF (testfile2, testfile2); + +/* testfile3 will be unlined by test1. */ +if (access (testfile3,F_OK )) +SAFE_OPEN (testfile3,O_CREAT |O_RDWR ,0600 ); + +/* subpathdir will be unlinked by test6. */ +if (access (subpathdir,F_OK )) +SAFE_MKDIR (subpathdir,0700 ); + }else + fds[2 ] =SAFE_OPEN (testfile3,O_CREAT |O_RDWR ,0600 ); + +/* testfile must exist except test1 and test6. */ +if (access (testfile,F_OK )) +SAFE_FILE_PRINTF (testfile, testfile); + +TEST (myunlinkat (fds[i], filenames[i], flags[i]));testcases/kernel/syscalls/unlinkat/unlinkat01.c static const int flags[] = { 0, 0, 0, 0, 9999, 0, · line 79
Quoted 10 lines
testcases/kernel/syscalls/unlinkat/unlinkat01.c +9
-0+if (TST_ERR == expected_errno[i]) +tst_res (TPASS |TTERRNO ,"unlinkat() returned expected errno" ); +else +tst_res (TFAIL |TTERRNO ,"unlinkat() failed" ); + +if (!expected_errno[i]) { +SAFE_CLOSE (fds[0 ]); + }else { +SAFE_CLOSE (fds[2 ]); }You can remove { } for consistency with previous.
Kind regards,
Petr
PATCH 1/1 syscalls/unlinkat01: Bugfix and update to new API
Hi Gongyi,
Quoted 3 lines
Hi Petr,
Thanks for your review!
yw :)
Quoted 15 lines
Quoted 14 lines
Review static const int flags[] = { 0, 0, 0, 0, 9999, 0, · line 41
Quoted 8 lines
(quoted diff) +0
-3-char *TCID = "unlinkat01"; -int TST_TOTAL = TEST_CASES; - static const char pathname[] = "unlinkattestdir", subpathname[] = "unlinkatsubtestdir", subpathdir[] = "unlinkattestdir/unlinkatsubtestdir",@@ -65,82 +41,79 @@ static const int flags[] = { 0, 0, 0, 0, 9999, 0, AT_REMOVEDIR };Could you please use static struct for testcases data which is the usual way in LTP instead of using arrays? (e.g. in
testcases/kernel/syscalls/access/access02.c).
It helps to the readability of the code as we'll be able to remove lines like:fds[1] = fds[4] = fds[6] = fds[0];
Quoted 7 lines
Quoted 3 lines
and most of the setup.
Than you can then drop also
TEST_CASES.It is more clearer that using arrays, but in this case, fds and filenames can not be complete initialized at first, so it seems there are some trouble to cleanup,
Chould you give me some suggestions for it?
How about adding functions to setup things and have pointer to the functions? See examples in testcases/kernel/syscalls/chmod/chmod06.c
or testcases/kernel/syscalls/clone/clone08.c
Kind regards,
Petr