From: Miao Xie <miaox@cn.fujitsu.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Josef Bacik <josef@redhat.com>,
Chris Mason <chris.mason@oracle.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Ito <t-itoh@jp.fujitsu.com>
Subject: Re: [PATCH] btrfs: fix dip leak
Date: Thu, 10 Mar 2011 10:54:26 +0800 [thread overview]
Message-ID: <4D783D62.2010709@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTikDN-v4C4rt-uTFQ35uoaoJ_9LRHSmAQUN4+uVD@mail.gmail.com>
On thu, 10 Mar 2011 00:46:42 +0800, Daniel J Blueman wrote:
> 2010/11/22 Miao Xie <miaox@cn.fujitsu.com>:
>> bio_endio() will free dip and dip->csums, so dip and dip->csums twice will
>> be freed twice. Fix it.
>>
>> Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
>> ---
>> fs/btrfs/inode.c | 9 +++------
>> 1 files changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
>> index 558cac2..5a5edc7 100644
>> --- a/fs/btrfs/inode.c
>> +++ b/fs/btrfs/inode.c
>> @@ -5731,7 +5731,7 @@ static void btrfs_submit_direct(int rw, struct bio *bio, struct inode *inode,
>>
>> ret = btrfs_bio_wq_end_io(root->fs_info, bio, 0);
>> if (ret)
>> - goto out_err;
>> + goto free_ordered;
>>
>> if (write && !skip_sum) {
>> ret = btrfs_wq_submit_bio(BTRFS_I(inode)->root->fs_info,
>> @@ -5740,7 +5740,7 @@ static void btrfs_submit_direct(int rw, struct bio *bio, struct inode *inode,
>> __btrfs_submit_bio_start_direct_io,
>> __btrfs_submit_bio_done);
>> if (ret)
>> - goto out_err;
>> + goto free_ordered;
>> return;
>> } else if (!skip_sum)
>> btrfs_lookup_bio_sums_dio(root, inode, bio,
>> @@ -5748,11 +5748,8 @@ static void btrfs_submit_direct(int rw, struct bio *bio, struct inode *inode,
>>
>> ret = btrfs_map_bio(root, rw, bio, 0, 1);
>> if (ret)
>> - goto out_err;
>> + goto free_ordered;
>> return;
>> -out_err:
>> - kfree(dip->csums);
>> - kfree(dip);
>> free_ordered:
>> /*
>> * If this is a write, we need to clean up the reserved space and kill
>
> The previous patch is broken and leaks dip when dip->csums allocation
> fails; bio->bi_end_io isn't set at the point where the free_ordered
> branch is consequently taken, thus bio_endio doesn't call the function
> which would free it in the normal case. Fix.
>
> Signed-off-by: Daniel J Blueman <daniel.blueman@gmail.com>
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index 0efdb65..53f4c8e 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -6056,6 +6056,7 @@ static void btrfs_submit_direct(int rw, struct
> bio *bio, struct inode *inode,
> if (!skip_sum) {
> dip->csums = kmalloc(sizeof(u32) * bio->bi_vcnt, GFP_NOFS);
> if (!dip->csums) {
> + kfree(dip);
> ret = -ENOMEM;
> goto free_ordered;
> }
Acked-by: Miao Xie <miaox@cn.fujitsu.com>
BTW: This bug had existed before applying my patch, so you should cc this mail
to the people who brought it, I think. He can do final check.
prev parent reply other threads:[~2011-03-10 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 16:46 [PATCH] btrfs: fix dip leak Daniel J Blueman
2011-03-10 2:54 ` Miao Xie [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=4D783D62.2010709@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=daniel.blueman@gmail.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=t-itoh@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).