Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs-progs: make some of the fsck-tests run without root
Date: Mon, 10 Apr 2023 14:11:30 -0400	[thread overview]
Message-ID: <cover.1681150198.git.josef@toxicpanda.com> (raw)

Hello,

While running tests on my ctree sync patches I noticed these tests were failing
when I ran as a normal user.  Most of them are just needing to call
setup_root_helper before calling the loop device helpers, some need a
$SUDO_HELPER added to a few places.  With these patches in place I can run make
test-fsck as a normal user.  Thanks,

Josef

Josef Bacik (4):
  btrfs-progs: fix fsck-tests/056 to run without root
  btrfs-progs: fix fsck-tests/057 to run without root
  btrfs-progs: fix fsck-tests/059 to run without root
  btrfs-progs: fix fsck-tests/060 to run without root

 tests/fsck-tests/056-raid56-false-alerts/test.sh | 6 +++---
 tests/fsck-tests/057-seed-false-alerts/test.sh   | 8 ++++----
 tests/fsck-tests/059-shrunk-device/test.sh       | 4 ++--
 tests/fsck-tests/060-degraded-check/test.sh      | 4 ++--
 4 files changed, 11 insertions(+), 11 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-04-10 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 18:11 Josef Bacik [this message]
2023-04-10 18:11 ` [PATCH 1/4] btrfs-progs: fix fsck-tests/056 to run without root Josef Bacik
2023-04-10 18:11 ` [PATCH 2/4] btrfs-progs: fix fsck-tests/057 " Josef Bacik
2023-04-10 18:11 ` [PATCH 3/4] btrfs-progs: fix fsck-tests/059 " Josef Bacik
2023-04-10 18:11 ` [PATCH 4/4] btrfs-progs: fix fsck-tests/060 " Josef Bacik
2023-04-11 17:00 ` [PATCH 0/4] btrfs-progs: make some of the fsck-tests " Neal Gompa
2023-04-11 23:56 ` David Sterba

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=cover.1681150198.git.josef@toxicpanda.com \
    --to=josef@toxicpanda.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox