From: Josef Bacik <jbacik@fusionio.com> To: Eric Sandeen <sandeen@redhat.com> Cc: Josef Bacik <jbacik@fusionio.com>, <linux-btrfs@vger.kernel.org>, <xfs@oss.sgi.com> Subject: Re: [PATCH 2/8] xfstests: add regression test for kernel bz 60673 Date: Mon, 21 Oct 2013 11:09:50 -0400 [thread overview] Message-ID: <20131021150950.GH6924@localhost.localdomain> (raw) In-Reply-To: <5265422E.8000101@redhat.com> On Mon, Oct 21, 2013 at 10:03:10AM -0500, Eric Sandeen wrote: > On 10/18/13 1:26 PM, Josef Bacik wrote: > > There was a problem with send trying to overwrite a file that wasn't actually > > the same. This is a test to check this particular case where receive fails when > > it should succeed properly. I tested this to verify it fails without my fix and > > passes with my fix. Thanks, > > 2 things - > > Why does the selinux context break things? That seems like a problem w/ send > if it can't work on a context-mounted fs? (disabling it for now doesn't bother > me, but I'm surprised that it's required). > So it is the context that xfstests is using, not contexts itself. Xfstests is using the nfs context, and using selinux contexts intercepts all getxattr calls, so when send tries to copy the xattrs for the file it calls getxattr, and because we are using the nfs context it returns EOPNOTSUPP from selinux, it never makes it down to btrfs. When using the actual real context it works fine because it calls down into the file system. > ((I also wonder if I should get rid of that context in general and use it only > for tests which fail without it)) > > Rather than all the cd'ing around (to /) what if you just do something like: > > SEND_TEST_DIR=$TEST_DIR/$tmp_dir/send > > mkdir $SEND_TEST_DIR > touch $SEND_TEST_DIR/baz > touch $SEND_TEST_DIR/blah > mkdir $SEND_TEST_DIR/foo > touch $SEND_TEST_DIR/foo/bar > > that seems a bit cleaner to me vs. the cd back and forth. > Yeah I can do that, thanks, Josef
WARNING: multiple messages have this Message-ID (diff)
From: Josef Bacik <jbacik@fusionio.com> To: Eric Sandeen <sandeen@redhat.com> Cc: linux-btrfs@vger.kernel.org, Josef Bacik <jbacik@fusionio.com>, xfs@oss.sgi.com Subject: Re: [PATCH 2/8] xfstests: add regression test for kernel bz 60673 Date: Mon, 21 Oct 2013 11:09:50 -0400 [thread overview] Message-ID: <20131021150950.GH6924@localhost.localdomain> (raw) In-Reply-To: <5265422E.8000101@redhat.com> On Mon, Oct 21, 2013 at 10:03:10AM -0500, Eric Sandeen wrote: > On 10/18/13 1:26 PM, Josef Bacik wrote: > > There was a problem with send trying to overwrite a file that wasn't actually > > the same. This is a test to check this particular case where receive fails when > > it should succeed properly. I tested this to verify it fails without my fix and > > passes with my fix. Thanks, > > 2 things - > > Why does the selinux context break things? That seems like a problem w/ send > if it can't work on a context-mounted fs? (disabling it for now doesn't bother > me, but I'm surprised that it's required). > So it is the context that xfstests is using, not contexts itself. Xfstests is using the nfs context, and using selinux contexts intercepts all getxattr calls, so when send tries to copy the xattrs for the file it calls getxattr, and because we are using the nfs context it returns EOPNOTSUPP from selinux, it never makes it down to btrfs. When using the actual real context it works fine because it calls down into the file system. > ((I also wonder if I should get rid of that context in general and use it only > for tests which fail without it)) > > Rather than all the cd'ing around (to /) what if you just do something like: > > SEND_TEST_DIR=$TEST_DIR/$tmp_dir/send > > mkdir $SEND_TEST_DIR > touch $SEND_TEST_DIR/baz > touch $SEND_TEST_DIR/blah > mkdir $SEND_TEST_DIR/foo > touch $SEND_TEST_DIR/foo/bar > > that seems a bit cleaner to me vs. the cd back and forth. > Yeah I can do that, thanks, Josef _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-21 15:09 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-18 18:26 [PATCH 1/8] xfstests: fix btrfs/002 to not use the scratch dev pool Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-18 18:26 ` [PATCH 2/8] xfstests: add regression test for kernel bz 60673 Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-21 15:03 ` Eric Sandeen 2013-10-21 15:03 ` Eric Sandeen 2013-10-21 15:09 ` Josef Bacik [this message] 2013-10-21 15:09 ` Josef Bacik 2013-10-21 15:14 ` Eric Sandeen 2013-10-21 15:14 ` Eric Sandeen 2013-10-21 15:21 ` Eric Sandeen 2013-10-21 15:21 ` Eric Sandeen 2013-10-18 18:26 ` [PATCH 3/8] xfstests: stat the dev we're removing to make sure its' really gone V2 Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-21 15:07 ` Eric Sandeen 2013-10-21 15:07 ` Eric Sandeen 2013-10-21 15:10 ` Josef Bacik 2013-10-21 15:10 ` Josef Bacik 2013-10-18 18:26 ` [PATCH 4/8] xfstests: btrfs/016: a hole punching send test Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-21 15:22 ` Eric Sandeen 2013-10-21 15:22 ` Eric Sandeen 2013-10-22 21:02 ` Rich Johnston 2013-10-22 21:02 ` Rich Johnston 2013-10-18 18:26 ` [PATCH 5/8] xfstests: generic/274 increase scratch fs size to 2g Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-21 15:29 ` Eric Sandeen 2013-10-21 15:29 ` Eric Sandeen 2013-10-22 20:25 ` Rich Johnston 2013-10-22 20:25 ` Rich Johnston 2013-10-18 18:26 ` [PATCH 6/8] xfstests: generic/311: add a few more test cases Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-21 15:37 ` Eric Sandeen 2013-10-21 15:37 ` Eric Sandeen 2013-10-18 18:26 ` [PATCH 7/8] xfstests: btrfs/017: add a regression test for snapshot creation Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-22 21:06 ` Rich Johnston 2013-10-22 21:06 ` Rich Johnston 2013-10-18 18:26 ` [PATCH 8/8] xfstests: btrfs/018: a regression test for subvolume rename Josef Bacik 2013-10-18 18:26 ` Josef Bacik 2013-10-21 15:38 ` Eric Sandeen 2013-10-21 15:38 ` Eric Sandeen 2013-10-22 21:09 ` Rich Johnston 2013-10-22 21:09 ` Rich Johnston 2013-10-22 20:57 ` [PATCH 1/8] xfstests: fix btrfs/002 to not use the scratch dev pool Rich Johnston 2013-10-22 20:57 ` Rich Johnston
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=20131021150950.GH6924@localhost.localdomain \ --to=jbacik@fusionio.com \ --cc=linux-btrfs@vger.kernel.org \ --cc=sandeen@redhat.com \ --cc=xfs@oss.sgi.com \ /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: linkBe 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.