From: Wang Sheng-Hui <shhuiw@gmail.com>
To: Jie Liu <jeff.liu@oracle.com>
Cc: sensille@gmx.net, chris.mason@fusionio.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: add malloc check in transaction.h/btrfs_start_transaction
Date: Thu, 16 Aug 2012 20:15:56 +0800 [thread overview]
Message-ID: <502CE47C.9070604@gmail.com> (raw)
In-Reply-To: <502CB573.8000107@oracle.com>
On 2012年08月16日 16:55, Jie Liu wrote:
> On 08/16/12 16:03, Arne Jansen wrote:
>> On 16.08.2012 09:57, Wang Sheng-Hui wrote:
>>> For malloc may fail, we should check it before assign
>>> values to the fields of struct btrfs_trans_handle *h.
>>>
>>> Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
>>> ---
>>> transaction.h | 5 +++++
>>> 1 files changed, 5 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/transaction.h b/transaction.h
>>> index a1070e0..d4e42a1 100644
>>> --- a/transaction.h
>>> +++ b/transaction.h
>>> @@ -32,7 +32,12 @@ static inline struct btrfs_trans_handle *
>>> btrfs_start_transaction(struct btrfs_root *root, int num_blocks)
>>> {
>>> struct btrfs_fs_info *fs_info = root->fs_info;
>>> +
> Why move down a blank line?
>>> struct btrfs_trans_handle *h = malloc(sizeof(*h));
> Skip a line here would looks a bit neat.
>>> + if (!h) {
>>> + BUG();
>>> + return NULL;
>>> + }
>> a more simple way would be to write
>> BUG_ON(!h);
>>
>>>
>>> BUG_ON(root->commit_root);
>>> BUG_ON(fs_info->running_transaction);
>> --
>> 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
>
Patch regenerated. Please check it. Thanks,
>From 5a265e252e87a8a456a6615affd57dfb49900c64 Mon Sep 17 00:00:00 2001
From: Wang Sheng-Hui <shhuiw@gmail.com>
Date: Thu, 16 Aug 2012 20:14:32 +0800
Subject: [PATCH] btrfs-progs: add malloc check in transaction.h/btrfs_start_transaction
For malloc may fail, we should check it before assign
values to the struct btrfs_trans_handle *h.
Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
---
transaction.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/transaction.h b/transaction.h
index a1070e0..e8610b1 100644
--- a/transaction.h
+++ b/transaction.h
@@ -34,6 +34,7 @@ btrfs_start_transaction(struct btrfs_root *root, int num_blocks)
struct btrfs_fs_info *fs_info = root->fs_info;
struct btrfs_trans_handle *h = malloc(sizeof(*h));
+ BUG_ON(!h);
BUG_ON(root->commit_root);
BUG_ON(fs_info->running_transaction);
fs_info->running_transaction = h;
--
1.7.1
prev parent reply other threads:[~2012-08-16 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 7:57 [PATCH] btrfs-progs: add malloc check in transaction.h/btrfs_start_transaction Wang Sheng-Hui
2012-08-16 8:03 ` Arne Jansen
2012-08-16 8:55 ` Jie Liu
2012-08-16 12:15 ` Wang Sheng-Hui [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=502CE47C.9070604@gmail.com \
--to=shhuiw@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=jeff.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.net \
/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).