All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wim Coekaerts <wim.coekaerts@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] posix
Date: Thu Jul  8 00:39:46 2004	[thread overview]
Message-ID: <20040708053933.GC24384@ca-server1.us.oracle.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8404D650E9@pdsmsx403>

awesome

On Thu, Jul 08, 2004 at 01:22:11PM +0800, Ling, Xiaofeng wrote:
> Many broken and fails are caused by unable chmod for the ocfs root directory.
> Such as access02, because the ocfs root can not write by other users.
> I've tried remove the restriction in ocfs_setattr, many case can pass.
> 
> >-----Original Message-----
> >From: wim.coekaerts@oracle.com [mailto:wim.coekaerts@oracle.com] 
> >Sent: 2004??7??7?? 17:12
> >To: Ling, Xiaofeng
> >Cc: Wim Coekaerts; ocfs2-devel@oss.oracle.com
> >Subject: Re: [Ocfs2-devel] posix
> >
> >great thanks - still a bunch that fail but compared to pervious list
> >this seems to behave much better.. hmm
> >i guess still a bunch of probs to address
> >
> >On Wed, Jul 07, 2004 at 04:44:06PM +0800, Ling, Xiaofeng wrote:
> >> >-----Original Message-----
> >> >any chance to rerun the ltp testsuites to see how we are doing these
> >> >days with all the changes ?
> >> >
> >> Follow is the output of LTP about file system call before  hang at
> >> readdir02.
> >> ---------------------------------------------------
> >> TDIRECTORY=/ocfs ./runalltests.sh -q -f `pwd`/runtest/syscall-file
> >> access01    1  PASS  :  access(accessfile, F_OK) returned 0
> >> access01    2  PASS  :  access(accessfile, X_OK) returned 0
> >> access01    3  PASS  :  access(accessfile, W_OK) returned 0
> >> access01    4  PASS  :  access(accessfile, R_OK) returned 0
> >> access02    1  BROK  :  open(test_file1, O_RDWR|O_CREAT, 
> >0644) Failed,
> >> errno=13 :Permission denied
> >> access02    2  BROK  :  Remaining cases broken
> >> access02    3  BROK  :  Remaining cases broken
> >> access02    4  BROK  :  Remaining cases broken
> >> access03    1  PASS  :  access((char *)-1,R_OK) failed as 
> >expected with

  reply	other threads:[~2004-07-08  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08  0:23 [Ocfs2-devel] posix Ling, Xiaofeng
2004-07-08  0:39 ` Wim Coekaerts [this message]
2004-07-13 16:59 ` Mark Fasheh
  -- strict thread matches above, loose matches on Subject: below --
2004-07-07  4:06 Ling, Xiaofeng
2004-07-07  4:11 ` Wim Coekaerts
2004-07-07  4:01 Ling, Xiaofeng
2004-07-06 11:51 Wim Coekaerts

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=20040708053933.GC24384@ca-server1.us.oracle.com \
    --to=wim.coekaerts@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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 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.