All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
	ocfs2-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [Ocfs2-devel] [PATCH 1/2] fiemap: Add new extent flag FIEMAP_EXTENT_SHARED
Date: Sat, 24 Oct 2009 19:30:39 +0100	[thread overview]
Message-ID: <20091024183039.GB30762@shareable.org> (raw)
In-Reply-To: <20091023180034.GA11402@wotan.suse.de>

Mark Fasheh wrote:
> On Wed, Oct 21, 2009 at 06:05:08PM -0700, Sunil Mushran wrote:
> > Patch adds flag FIEMAP_EXTENT_SHARED to denote extents that are
> > shared with other inodes.
> 
> This looks pretty sane to me. Thanks Sunil.

It might be better to have a flag FIEMAP_EXTENT_NOT_SHARED.

Apps which need to know the data is not shared can't safely check
!(flags & FIEMAP_EXTENT_SHARED) because of old kernels which don't set
the flag.

-- Jamie

WARNING: multiple messages have this Message-ID (diff)
From: Jamie Lokier <jamie@shareable.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
	ocfs2-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Ocfs2-devel] [PATCH 1/2] fiemap: Add new extent flag FIEMAP_EXTENT_SHARED
Date: Sat, 24 Oct 2009 19:30:39 +0100	[thread overview]
Message-ID: <20091024183039.GB30762@shareable.org> (raw)
In-Reply-To: <20091023180034.GA11402@wotan.suse.de>

Mark Fasheh wrote:
> On Wed, Oct 21, 2009 at 06:05:08PM -0700, Sunil Mushran wrote:
> > Patch adds flag FIEMAP_EXTENT_SHARED to denote extents that are
> > shared with other inodes.
> 
> This looks pretty sane to me. Thanks Sunil.

It might be better to have a flag FIEMAP_EXTENT_NOT_SHARED.

Apps which need to know the data is not shared can't safely check
!(flags & FIEMAP_EXTENT_SHARED) because of old kernels which don't set
the flag.

-- Jamie

  reply	other threads:[~2009-10-24 18:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22  1:05 [Ocfs2-devel] Extend FIEMAP to indicate shared extents Sunil Mushran
2009-10-22  1:05 ` Sunil Mushran
2009-10-22  1:05 ` [Ocfs2-devel] [PATCH 1/2] fiemap: Add new extent flag FIEMAP_EXTENT_SHARED Sunil Mushran
2009-10-22  1:05   ` Sunil Mushran
2009-10-23 18:00   ` [Ocfs2-devel] " Mark Fasheh
2009-10-23 18:00     ` Mark Fasheh
2009-10-24 18:30     ` Jamie Lokier [this message]
2009-10-24 18:30       ` Jamie Lokier
2009-10-26 17:29       ` Sunil Mushran
2009-10-26 17:29         ` Sunil Mushran
2009-10-26 17:29         ` [Ocfs2-devel] " Sunil Mushran
2009-10-26 19:29         ` Brad Boyer
2009-10-26 19:29           ` Brad Boyer
2009-10-22  1:05 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: Use FIEMAP_EXTENT_SHARED Sunil Mushran
2009-10-22  1:05   ` Sunil Mushran
  -- strict thread matches above, loose matches on Subject: below --
2009-11-06 23:24 [Ocfs2-devel] Extend FIEMAP to indicate shared extents Sunil Mushran
2009-11-06 23:24 ` [Ocfs2-devel] [PATCH 1/2] fiemap: Add new extent flag FIEMAP_EXTENT_SHARED Sunil Mushran
2009-12-03 20:46 [Ocfs2-devel] Add FIEMAP_EXTENT_SHARED flag Sunil Mushran
2009-12-03 20:46 ` [Ocfs2-devel] [PATCH 1/2] fiemap: Add new extent flag FIEMAP_EXTENT_SHARED Sunil Mushran

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=20091024183039.GB30762@shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=sunil.mushran@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.