public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Peng Tao <bergwolf@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>, Peng Tao <bergwolf@gmail.com>
Subject: [PATCH] add comments for extent_fiemap
Date: Wed,  3 Jun 2009 10:52:37 +0800	[thread overview]
Message-ID: <1243997557-5961-1-git-send-email-bergwolf@gmail.com> (raw)

This also explains btrfs fiemap ioctl() return values, especially the positive
return value, which may confuse users.

Signed-off-by: Peng Tao <bergwolf@gmail.com>
---
 fs/btrfs/extent_io.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index 6826018..287896e 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -2828,6 +2828,11 @@ out:
 	return sector;
 }
 
+/*
+ * Get the extents count of a file and map the extent to a user-supplied extent
+ * array. Returns 0 on success, 1 when the user-supplied extents array is full,
+ * and negetive values on failure.
+ */
 int extent_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
 		__u64 start, __u64 len, get_extent_t *get_extent)
 {
-- 
1.6.2.GIT


                 reply	other threads:[~2009-06-03  2:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1243997557-5961-1-git-send-email-bergwolf@gmail.com \
    --to=bergwolf@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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