From: Miao Xie <miaox@cn.fujitsu.com>
To: Dan Carpenter <error27@gmail.com>,
Chris Mason <chris.mason@oracle.com>,
Yan Zheng <zheng.yan@oracle.com>,
Diego Calleja <diegocg@gmail.com>,
linux-btrfs@vger.kernel.org, linux-kerne
Subject: Re: [patch] btrfs: make code reachable in btrfs_insert_some_items()
Date: Tue, 29 Jun 2010 08:57:54 +0800 [thread overview]
Message-ID: <4C294512.8070302@cn.fujitsu.com> (raw)
In-Reply-To: <20100628111726.GI19184@bicker>
Hi,
on 2010-6-28 19:17, Dan Carpenter wrote:
> The break was in front of the "nr = i" assignment so that was never hit.
This bug has been fixed a month ago, and the patch has been merged into the
btrfs-unstable tree.
http://marc.info/?l=linux-btrfs&m=127434036913484&w=2
Thanks
Miao
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
>
> diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
> index 0d1d966..ceb8ad2 100644
> --- a/fs/btrfs/ctree.c
> +++ b/fs/btrfs/ctree.c
> @@ -3453,8 +3453,8 @@ int btrfs_insert_some_items(struct btrfs_trans_handle *trans,
> for (i = 0; i < nr; i++) {
> if (total_size + data_size[i] + sizeof(struct btrfs_item) >
> BTRFS_LEAF_DATA_SIZE(root)) {
> - break;
> nr = i;
> + break;
> }
> total_data += data_size[i];
> total_size += data_size[i] + sizeof(struct btrfs_item);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Miao Xie <miaox@cn.fujitsu.com>
To: Dan Carpenter <error27@gmail.com>,
Chris Mason <chris.mason@oracle.com>,
Yan Zheng <zheng.yan@oracle.com>,
Diego Calleja <diegocg@gmail.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] btrfs: make code reachable in btrfs_insert_some_items()
Date: Tue, 29 Jun 2010 08:57:54 +0800 [thread overview]
Message-ID: <4C294512.8070302@cn.fujitsu.com> (raw)
In-Reply-To: <20100628111726.GI19184@bicker>
Hi,
on 2010-6-28 19:17, Dan Carpenter wrote:
> The break was in front of the "nr = i" assignment so that was never hit.
This bug has been fixed a month ago, and the patch has been merged into the
btrfs-unstable tree.
http://marc.info/?l=linux-btrfs&m=127434036913484&w=2
Thanks
Miao
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
>
> diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
> index 0d1d966..ceb8ad2 100644
> --- a/fs/btrfs/ctree.c
> +++ b/fs/btrfs/ctree.c
> @@ -3453,8 +3453,8 @@ int btrfs_insert_some_items(struct btrfs_trans_handle *trans,
> for (i = 0; i < nr; i++) {
> if (total_size + data_size[i] + sizeof(struct btrfs_item) >
> BTRFS_LEAF_DATA_SIZE(root)) {
> - break;
> nr = i;
> + break;
> }
> total_data += data_size[i];
> total_size += data_size[i] + sizeof(struct btrfs_item);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-29 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 11:17 [patch] btrfs: make code reachable in btrfs_insert_some_items() Dan Carpenter
2010-06-29 0:57 ` Miao Xie [this message]
2010-06-29 0:57 ` Miao Xie
2010-06-29 1:04 ` Chris Mason
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=4C294512.8070302@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=diegocg@gmail.com \
--cc=error27@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zheng.yan@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.