All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xu Wang <xuw@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] fs: Fix the check bug in testcases/kernel/fs/acl/tacl_xattr.sh
Date: Fri, 10 Oct 2014 04:06:48 -0400 (EDT)	[thread overview]
Message-ID: <449596914.42340372.1412928408912.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1514362509.42340352.1412928396918.JavaMail.zimbra@redhat.com>

From fbc38181f0504d5e92def922977da2dd0ae0ee8b Mon Sep 17 00:00:00 2001
From: George Wang <xuw@redhat.com>
Date: Fri, 10 Oct 2014 15:59:16 +0800
Subject: [PATCH]  fs: Fix the check bug in
 testcases/kernel/fs/acl/tacl_xattr.sh

Signed-off-by: George Wang <xuw@redhat.com>
---
 testcases/kernel/fs/acl/tacl_xattr.sh | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/testcases/kernel/fs/acl/tacl_xattr.sh b/testcases/kernel/fs/acl/tacl_xattr.sh
index 99f6a95..5a60a04 100755
--- a/testcases/kernel/fs/acl/tacl_xattr.sh
+++ b/testcases/kernel/fs/acl/tacl_xattr.sh
@@ -247,24 +247,24 @@ su - tacluser1 << TACL_USER1
    if [ -e $CUR_PATH/tacl/mount-ext2/shared/team1/newfile1 ]
    then
        echo ""
-       echo "FAILED:  [ touch ] ACL_USER_OBJ  entry already contains the owner write "
-       echo -e "\t permissions, but operation failed [ Physical Directory ]"
-   else
-       echo ""
        echo "SUCCESS: ACL_USER_OBJ  entry contains the owner write permissions,"
        echo -e "\t operation success [ Physical Directory ]"
+   else
+       echo ""
+       echo "FAILED:  [ touch ] ACL_USER_OBJ  entry already contains the owner write "
+       echo -e "\t permissions, but operation failed [ Physical Directory ]"
    fi

    touch $CUR_PATH/tacl/mount-ext2/shared/symlinkdir1/newfil2 2> /dev/null
    if [ -e $CUR_PATH/tacl/mount-ext2/shared/team1/newfile2 ]
    then
        echo ""
-       echo "FAILED:  [ touch ] ACL_USER_OBJ  entry already contains the owner write "
-       echo -e "\t permissions, but operation failed [ Symlink Directory ]"
-   else
-       echo ""
        echo "SUCCESS: ACL_USER_OBJ  entry contains the owner write permissions,"
        echo -e "\t operation success [ Symlink Directory ]"
+   else
+       echo ""
+       echo "FAILED:  [ touch ] ACL_USER_OBJ  entry already contains the owner write "
+       echo -e "\t permissions, but operation failed [ Symlink Directory ]"
    fi

 TACL_USER1
-- 
1.9.3

-- 
George Wang 王旭

Kernel Quantity Engineer
Red Hat Software (Beijing) Co.,Ltd
IRC:xuw
Tel:+86-010-62608041
Phone:15901231579
9/F, Tower C, Raycom


------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

       reply	other threads:[~2014-10-10  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1514362509.42340352.1412928396918.JavaMail.zimbra@redhat.com>
2014-10-10  8:06 ` Xu Wang [this message]
2014-10-14  7:51   ` [LTP] [PATCH] fs: Fix the check bug in testcases/kernel/fs/acl/tacl_xattr.sh Eryu Guan
2014-10-14 12:57   ` Jan Stancek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=449596914.42340372.1412928408912.JavaMail.zimbra@redhat.com \
    --to=xuw@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.