From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH] fstests: btrfs/012 don't follow symlinks for populating $SCRATCH_MNT
Date: Sat, 25 Mar 2023 10:06:47 -0700 [thread overview]
Message-ID: <20230325170647.GA16170@frogsfrogsfrogs> (raw)
In-Reply-To: <ZB6ubFfBIvFLqs73@infradead.org>
On Sat, Mar 25, 2023 at 01:18:52AM -0700, Christoph Hellwig wrote:
> On Fri, Mar 24, 2023 at 04:13:19PM -0400, Josef Bacik wrote:
> > /lib/modules/$(uname -r)/ can have symlinks to the source tree where the
> > kernel was built from, which can have all sorts of stuff, which will
> > make the runtime for this test exceedingly long. We're just trying to
> > copy some data into our tree to test with, we don't need the entire
> > devel tree of whatever we're doing, so use -P to not follow symlinks
> > when copying.
>
> Btw, if you're touching this test can you make it _notrun if the
> directory doesn't exist? This test always fails for VMs without
> any modules.
If you just want some filler content for the "old" ext4 filesystem, why
not simply copy something that's guaranteed to exist like /etc or /var?
And perhaps use timeout(1) to control the cp runtime?
(I don't have the symlink problem, but I occasionally watch this test
suddenly take forever if I accidentally turn off module compression
and/or slim debuginfo...)
--D
prev parent reply other threads:[~2023-03-25 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 20:13 [PATCH] fstests: btrfs/012 don't follow symlinks for populating $SCRATCH_MNT Josef Bacik
2023-03-24 20:46 ` Roman Mamedov
2023-03-25 4:36 ` Zorro Lang
2023-03-25 8:18 ` Christoph Hellwig
2023-03-25 17:06 ` Darrick J. Wong [this message]
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=20230325170647.GA16170@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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.