hi,
On Wed, 2015-03-11 at 13:30 +0100, Cyril Hrubis wrote:
> Hi!
> >
> > +SELINUX=$(getenforce)
>
> There are systems without selinux support that does not have this
> command available. You should check if setenforce and getenforce is
> present on the system first, then you can try to set the selinux to
> permissive.
Hmm, how about these two ways, which one is better?
1.
if [ -x "/usr/sbin/getenforce" -a -x "/usr/sbin/setenforce" ]; then
SELINUX=`getenforce`
else
SELINUX=""
fi
2.
COMMAND=$(command -v "getenforce" "setenforce" |wc -l)
if [ $COMMAND -eq 2 ]; then
SELINUX=$(getenforce)
else
SELINUX=""
fi
>
> > do_setup(){
> >
> > + tst_require_root
> > +
> > rm -f $FILE_ACL
> > rm -f $FILE_ACL_LINK
> >
> > + # We couldn't consider whether the SElinux is Disable or Permissive.
> > + # We only set it to Permissive when it it Enforcing.
> > + if [ "$SELINUX" = "Enforcing" ]; then
> > + echo "set the SElinux to Permissive."
> > + setenforce 0
> > + fi
> > +
> > if [ "x$TEST_USER1_HOMEDIR" = "x" ]; then
> > - echo "Could not find user $TEST_USER1's home directory."
> > - exit 1
> > + tst_brkm TCONF "Could not find user $TEST_USER1's home
> > directory."
> > fi
> >
> > # XXX (garrcoop): why is cleanup junk being done in setup??? Bad test!!!
> > @@ -73,8 +85,7 @@ do_setup(){
> > useradd -d $TEST_USER1_HOMEDIR -m -g $TEST_USER1_GROUP $TEST_USER1 -s
> > /bin/sh
> >
> > if [ $? -ne 0 ]; then
> > - echo "Could not add test user $TEST_USER1."
> > - exit 1
> > + tst_brkm TCONF "Could not add test user $TEST_USER1."
> > fi
>
> I guess that these should rather rather be TBROK than TCONF. Or is the
> useradd failure expected to happen?
Of course not, useradd failure is not expected. I agree with your point.
Seems like I should read the documents again to understand the
distinguish of TBROK/TCONF in tst_brkm/tst_resm. thank you so much!
>
> > }
> > @@ -91,6 +102,12 @@ do_cleanup() {
> > mount | grep "$TMP/tacl/mount-ext3" && umount -d $TMP/tacl/mount-ext3
> > [ "x$LOOP_DEV" != x ] && losetup -d $LOOP_DEV
> > rm -rf $TMP/tacl
> > +
> > + # We set it back to Enforcing.
> > + if [ "$SELINUX" = "Enforcing" ]; then
> > + echo "set the SElinux back to Enforcing."
> > + setenforce 1
> > + fi
> > }
> >
> > #-----------------------------------------------------------------------
> > @@ -103,13 +120,11 @@ then
> > echo ""
> > else
> > if [ $(id -ru) != 0 ]; then
> > - tst_resm TCONF "must be root to execute this script"
> > - exit 0
> > + tst_brkm TCONF "Must be root to execute this script"
> > fi
>
> We have tst_require_root() in test.sh, please use it.
ok.
>
> > if ! ( test -d $TMP/tacl || mkdir -m 777 $TMP/tacl) ; then
> > - tst_resm TCONF "failed to create $TMP/tacl directory."
> > - exit 1
> > + tst_brkm TCONF "Failed to create $TMP/tacl directory."
> > fi
>
> This looks more like TBROK as well. And even better the test should use
> tst_tmpdir() and tst_rmdir() to create temporary directories.
sorry, I don't know how to replace the $TMP/tacl by tst_rmdir() function
in this test.
any detail instruction here?
>
> > trap do_cleanup EXIT
> > @@ -119,21 +134,18 @@ else
> >
> > dd if=/dev/zero of=$TMP/tacl/blkext3 bs=1k count=10240 && chmod 777
> > $TMP/tacl/blkext3
> > if [ $? -ne 0 ] ; then
> > - tst_resm TCONF "Failed to create $TMP/tacl/blkext3"
> > - exit 0
> > + tst_brkm TCONF "Failed to create $TMP/tacl/blkext3"
> > fi
>
> Looks like TBROK to me as well.
agree!
>
> > # Avoid hardcoded loopback device values (-f tries to find the first
> > # available loopback device name)!
> > if ! LOOP_DEV=$(losetup -f) || [ "x$LOOP_DEV" = x ]; then
> > - tst_resm TCONF "[ losetup.1 ] Failed to find an available
> > loopback device -- is the required support compiled in your kernel?"
> > - exit 0
> > + tst_brkm TCONF "[ losetup.1 ] Failed to find an available
> > loopback device -- is the required support compiled in your kernel?"
> > fi
> >
> > if ! losetup $LOOP_DEV $TMP/tacl/blkext3 2>&1 > /dev/null; then
> > echo ""
> > - tst_resm TCONF "[ losetup.2 ] Failed to setup the device."
> > - exit 0
> > + tst_brkm TCONF "[ losetup.2 ] Failed to setup the device."
> > fi
> >
> > mount | grep ext2
> > @@ -180,20 +192,18 @@ then
> > ${TCbin}/acl_file_test $FILE_ACL
> > if [ $? -ne 0 ]
> > then
> > - EXIT_CODE=1
> > - echo "Extended acls for files (FAILED)"
> > + tst_brkm TFAIL "Extended acls for files."
>
> Why tst_brkm here? It should rather be tst_resm so that the test
> continues with the rest of testcases. The original code didn't
> exit the test here.
agree all the below comments.
>
> > else
> > - echo "Extended acls for files (PASSED)"
> > + tst_resm TPASS "Extended acls for files."
> > fi
> >
> > echo "Trying extended acls for file links"
> > ${TCbin}/acl_link_test $FILE_ACL_LINK
> > if [ $? -ne 0 ]
> > then
> > - EXIT_CODE=1
> > - echo "Extended acls for links (FAILED)"
> > + tst_brkm TFAIL "Extended acls for links."
>
> Here as well.
>
> > else
> > - echo "Extended acls for links (PASSED)"
> > + tst_resm TPASS "Extended acls for links."
> > fi
> > else
> > do_setup
> > @@ -211,20 +221,18 @@ else
> > ${TCbin}/acl_file_test $FILE_ACL
> > if [ $? -ne 0 ]
> > then
> > - EXIT_CODE=1
> > - echo "Extended acls for files (FAILED)"
> > + tst_brkm TFAIL "Extended acls for files."
>
> And here as well.
>
> > else
> > - echo "Extended acls for files (PASSED)"
> > + tst_resm TPASS "Extended acls for files."
> > fi
> >
> > echo "Trying extended acls for file links"
> > ${TCbin}/acl_link_test $FILE_ACL_LINK
> > if [ $? -ne 0 ]
> > then
> > - EXIT_CODE=1
> > - echo "Extended acls for links (FAILED)"
> > + tst_brkm TFAIL "Extended acls for links."
>
> Here as well.
>
> > else
> > - echo "Extended acls for links (PASSED)"
> > + tst_resm TPASS "Extended acls for links."
> > fi
> >
> > chown $TEST_USER1 $FILE_ACL
> > @@ -235,4 +243,4 @@ else
> > do_cleanup
> > fi
> >
> > -exit $EXIT_CODE
> > +tst_exit
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
