7b44b6c16f
In stub, for fops like readv, writev etc, if the the object is bad, then the fop is denied. But for checking if the object is bad inode context should be checked. Now, if the inode context is not there, then the fop is allowed to continue. This patch fixes it and the fop is unwound with an error, if the inode context is not found. Change-Id: I5ea4d4fc1a91387f7f9d13ca8cb43c88429f02b0 BUG: 1243391 Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com> Reviewed-on: http://review.gluster.org/11449 Tested-by: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Venky Shankar <vshankar@redhat.com>
43 lines
1.1 KiB
Bash
43 lines
1.1 KiB
Bash
#!/bin/bash
|
|
|
|
. $(dirname $0)/../include.rc
|
|
. $(dirname $0)/../volume.rc
|
|
|
|
cleanup;
|
|
|
|
TEST glusterd
|
|
TEST pidof glusterd
|
|
|
|
## Create a distribute volume (B=2)
|
|
TEST $CLI volume create $V0 $H0:$B0/${V0}1 $H0:$B0/${V0}2;
|
|
EXPECT "$V0" volinfo_field $V0 'Volume Name';
|
|
EXPECT 'Created' volinfo_field $V0 'Status';
|
|
EXPECT '2' brick_count $V0
|
|
|
|
|
|
## Start the volume
|
|
TEST $CLI volume start $V0;
|
|
EXPECT 'Started' volinfo_field $V0 'Status';
|
|
|
|
## Mount the volume
|
|
TEST $GFS --volfile-server=$H0 --volfile-id=$V0 $M0;
|
|
|
|
echo "123" >> $M0/file;
|
|
|
|
TEST ! setfattr -n "trusted.glusterfs.set-signature" -v "123" $M0/file;
|
|
TEST ! setfattr -n "trusted.glusterfs.get-signature" -v "123" $M0/file;
|
|
|
|
# sign xattr
|
|
TEST ! setfattr -n "trusted.bit-rot.signature" -v "123" $M0/file;
|
|
TEST ! setfattr -x "trusted.bit-rot.signature" $M0/file;
|
|
|
|
# versioning xattr
|
|
TEST ! setfattr -n "trusted.bit-rot.version" -v "123" $M0/file;
|
|
TEST ! setfattr -x "trusted.bit-rot.version" $M0/file;
|
|
|
|
# bad file xattr
|
|
TEST ! setfattr -n "trusted.bit-rot.bad-file" -v "123" $M0/file;
|
|
TEST ! setfattr -x "trusted.bit-rot.bad-file" $M0/file;
|
|
|
|
cleanup;
|