From: Christoph Hellwig <hch@infradead.org>
To: Dwight Engen <dwight.engen@oracle.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfstests 317
Date: Fri, 25 Oct 2013 02:33:33 -0700 [thread overview]
Message-ID: <20131025093333.GB24583@infradead.org> (raw)
In-Reply-To: <20131024162557.6dd72435@oracle.com>
On Thu, Oct 24, 2013 at 04:25:57PM -0400, Dwight Engen wrote:
> On Thu, 24 Oct 2013 09:12:35 -0700
> Christoph Hellwig <hch@infradead.org> wrote:
>
> > This one also seems to be guranteed to fail for me with the following
> > output:
> >
> >
> > --- tests/generic/317.out 2013-09-09 14:41:08.000000000 +0000
> > +++ /root/xfstests/results//generic/317.out.bad 2013-10-24
> > 16:12:00.000000000 +0000 @@ -4,9 +4,7 @@
> > Size: 0 Filetype: Regular File
> > Mode: (0644/-rw-r--r--) Uid: (qa_user) Gid: (qa_user)
> > From user_ns
> > - File: "$SCRATCH_MNT/file1"
> > - Size: 0 Filetype: Regular File
> > - Mode: (0644/-rw-r--r--) Uid: (0) Gid: (0)
> > +execvp: Permission denied
>
> Hi Christoph,
>
> Hmm, this looks to me like src/lstat64 cannot be exec()ed by qa_user on
> your system. Is there some other id I can/should use?
That doesn't seem to be the issue from the main system for me:
root@vm:~/xfstests# sudo -u fsgqa ./src/lstat64
Usage: lstat64 [-t] filename ...
Do you have a one liner to try what happens in a namespace?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2013-10-25 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131024161235.GA29381@infradead.org>
[not found] ` <20131024162557.6dd72435@oracle.com>
2013-10-25 9:33 ` Christoph Hellwig [this message]
2013-10-28 15:43 ` xfstests 317 Dwight Engen
2013-10-30 16:19 ` Christoph Hellwig
2013-10-30 16:24 ` Christoph Hellwig
2013-10-30 18:30 ` [PATCH] xfstests: generic/317 use relative paths to avoid traversal permission problems Dwight Engen
2013-10-31 15:40 ` Christoph Hellwig
2013-11-04 20:43 ` 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=20131025093333.GB24583@infradead.org \
--to=hch@infradead.org \
--cc=dwight.engen@oracle.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: 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