public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org
Subject: Re: Does _need_to_be_root deserve to live?
Date: Thu, 11 Feb 2016 17:15:51 +0800	[thread overview]
Message-ID: <20160211091551.GA11419@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160211035746.GA16082@thunk.org>

On Wed, Feb 10, 2016 at 10:57:46PM -0500, Theodore Ts'o wrote:
> There appear to be a number of tests that need to mount and unmount
> scratch or su to $qa_user that don't call the helper _need_to_be_root.
> 
> Also, sicne the check script calls _check_filesystems between every
> single test, which requires unmounting and remounting the test and/or
> scratch file systems, does the _need_to_be_root check make any sense
> at all?
> 
> And if doesn't make any sense, is it worth it to submitting a patch
> that just removes all mention of _need_to_be_root from the tests and
> common/rc?

I think it's safe to remove all _need_to_be_root calls, because there's
already a user-id check in "check"

346 if [ `id -u` -ne 0 ]
347 then
348     echo "check: QA must be run as root"
349     exit 1
350 fi

Thanks,
Eryu

      reply	other threads:[~2016-02-11  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11  3:57 Does _need_to_be_root deserve to live? Theodore Ts'o
2016-02-11  9:15 ` Eryu Guan [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=20160211091551.GA11419@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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