All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@sysam.it>
To: Dave Chinner <david@fromorbit.com>, Eric Sandeen <sandeen@sandeen.net>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: help on xfs test results
Date: Mon, 05 Oct 2015 19:15:08 +0200	[thread overview]
Message-ID: <5612B01C.50600@sysam.it> (raw)
In-Reply-To: <20151002003834.GI3902@dastard>

Hi Dave, Eric and all,

still thanks.

About generic/256 failing in my system,

in the xfstests README there is:

- create fsgqa test user ("sudo useradd fsgqa")

this creates the user, but in /etc/passwd comes "/bin/sh" as shell,
and in this system is it "dash". Redirection to /dev/null as required
from this test then fails. Setting to "/bin/bash" test passes.


About xfs/136,

ack, thanks.



On 02/10/2015 02:38, Dave Chinner wrote:
> On Thu, Oct 01, 2015 at 07:31:13PM -0500, Eric Sandeen wrote:
>>
>>
>> On 10/1/15 6:56 PM, Dave Chinner wrote:
>>> Are you testing with something like selinux or some other security
>>> subsystem enabled that creates attributes at inode creation time?
>>
>> In theory, xfstests detects this and mounts with an fs-wide context
>> to avoid that...
>
> For selinux, yes. i don't think it's aware of anything else,
> though...
>
> Cheers,
>
> Dave.
>


Best regards
Angelo


  reply	other threads:[~2015-10-05 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <560C69D9.6020807@sysam.it>
2015-10-01  8:48 ` help on xfs test results Angelo Dureghello
2015-10-01 23:56   ` Dave Chinner
2015-10-02  0:31     ` Eric Sandeen
2015-10-02  0:38       ` Dave Chinner
2015-10-05 17:15         ` Angelo Dureghello [this message]
2015-09-29 23:03 Angelo Dureghello
2015-09-29 23:28 ` Dave Chinner

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=5612B01C.50600@sysam.it \
    --to=angelo@sysam.it \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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.