From: jim owens <jowens@hp.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [RFC 02/12 RESEND PATCH] Btrfs: __btrfs_map_block should not set length more than input length.
Date: Mon, 04 Jan 2010 16:12:45 -0500 [thread overview]
Message-ID: <4B4259CD.4010104@hp.com> (raw)
Returning a value greater than the caller's is ugly and prone
to dangerous future coding mistakes.
Signed-off-by: jim owens <jowens@hp.com>
---
fs/btrfs/extent-tree.c | 3 ---
fs/btrfs/inode.c | 5 ++---
fs/btrfs/volumes.c | 9 +++++----
3 files changed, 7 insertions(+), 10 deletions(-)
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 56e5013..b610557 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -1600,9 +1600,6 @@ static int btrfs_discard_extent(struct btrfs_root *root, u64 bytenr,
struct btrfs_bio_stripe *stripe = multi->stripes;
int i;
- if (map_length > num_bytes)
- map_length = num_bytes;
-
for (i = 0; i < multi->num_stripes; i++, stripe++) {
btrfs_issue_discard(stripe->dev->bdev,
stripe->physical,
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index 5440bab..152015c 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -1397,20 +1397,19 @@ int btrfs_merge_bio_hook(struct page *page, unsigned long offset,
struct btrfs_root *root = BTRFS_I(page->mapping->host)->root;
struct btrfs_mapping_tree *map_tree;
u64 logical = (u64)bio->bi_sector << 9;
- u64 length = 0;
+ u64 length = bio->bi_size + size;
u64 map_length;
int ret;
if (bio_flags & EXTENT_BIO_COMPRESSED)
return 0;
- length = bio->bi_size;
map_tree = &root->fs_info->mapping_tree;
map_length = length;
ret = btrfs_map_block(map_tree, READ, logical,
&map_length, NULL, 0);
- if (map_length < length + size)
+ if (ret || map_length < length)
return 1;
return 0;
}
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index f4b5666..5af76fc 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -2697,14 +2697,15 @@ again:
/* stripe_offset is the offset of this block in its stripe*/
stripe_offset = offset - stripe_offset;
+ /* return smaller of input length or remaining contiguous length */
if (map->type & (BTRFS_BLOCK_GROUP_RAID0 |
BTRFS_BLOCK_GROUP_RAID10)) {
- /* we limit the length of each bio to what fits in a stripe */
- *length = min_t(u64, em->len - offset,
- map->stripe_len - stripe_offset);
+ /* only the length that fits in one stripe is contiguous */
+ *length = min(*length, min_t(u64, em->len - offset,
+ map->stripe_len - stripe_offset));
} else {
/* RAID1, DUP, and simple disk stripes are all contiguous */
- *length = em->len - offset;
+ *length = min(*length, em->len - offset);
}
if (!multi_ret && !unplug_page)
--
1.5.6.3
reply other threads:[~2010-01-04 21:12 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=4B4259CD.4010104@hp.com \
--to=jowens@hp.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 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.