All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@google.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ext2 attributes for OCFS2
Date: Wed, 14 Jun 2006 12:08:06 -0700	[thread overview]
Message-ID: <44905E96.9040002@google.com> (raw)
In-Reply-To: <20060614185431.GE3082@ca-server1.us.oracle.com>

Mark Fasheh wrote:
> On Wed, Jun 14, 2006 at 12:44:00PM +0200, Herbert Poetzl wrote:
>>>Yeah, it should mostly work just fine, but I'm betting there are some
>>>paths which will need a manual re-check as things may have changed out
>>>from under the VFS while we weren't holding a cluster lock. It should
>>>be easy enough to check things like the immutable flag in those places
>>>though.
>>
>>might be, I already wondered why things like
>>mark_inode_dirty() do not work with ocfs2,
>>IMHO the vfs/ocfs2 synchronization is broken
>>(to some degree) but maybe that is intentional
> 
> Yeah, it's difficult to get the VFS to "cluster lock" without affecting the
> runtime of other file systems, so we have to work within that constraint :/

Please don't be shy about asking.  Can you describe the mark_inode_dirty
issue?

Regards,

Daniel

      reply	other threads:[~2006-06-14 19:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10 12:32 [Ocfs2-devel] ext2 attributes for OCFS2 Herbert Poetzl
2006-06-11 17:45 ` Mark Fasheh
2006-06-12 21:41   ` Herbert Poetzl
2006-06-13 23:56     ` Mark Fasheh
2006-06-14 10:44       ` Herbert Poetzl
2006-06-14 18:54         ` Mark Fasheh
2006-06-14 19:08           ` Daniel Phillips [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=44905E96.9040002@google.com \
    --to=phillips@google.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.