All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [BUG] can not chmod to 777
Date: Wed Apr 14 18:09:28 2004	[thread overview]
Message-ID: <407DC414.4020508@oracle.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F843C28A5@PDSMSX403.ccr.corp.intel.com>

I agree with kurt about adding a lockfe for making changes
in the volhdr. But short of that, if all you are doing is single
node tests, just hack it. As in, comment out the root inode
check in ocfs_setattr and also jump over any code making
fe changes on disk for this. There is no fe for root in ocfs.

This should help in reducing the noise in ltp.

Ling, Xiaofeng wrote:

>HI
>	I create a directory /ocfs, and take it the mount point of ocfs2
>filesystem, but I can not
>use "chmod 777" to change its permission, it always shows 755.
>Seems this breaks a lot LTP test cases.
>I report it as bug 56.
>_______________________________________________
>Ocfs2-devel mailing list
>Ocfs2-devel@oss.oracle.com
>http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>  
>

      parent reply	other threads:[~2004-04-14 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 20:47 [Ocfs2-devel] [BUG] can not chmod to 777 Ling, Xiaofeng
2004-04-13 21:21 ` Kurt Hackel
2004-04-14 14:12   ` Sunil Mushran
2004-04-14 14:22     ` Kurt Hackel
2004-04-14 18:09 ` Sunil Mushran [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=407DC414.4020508@oracle.com \
    --to=sunil.mushran@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.