From: Wang Shilong <wangshilong1991@gmail.com>
To: Azat Khuzhin <a3at.mail@gmail.com>
Cc: Wang Shilong <wangsl.fnst@cn.fujitsu.com>,
open list <linux-kernel@vger.kernel.org>,
Chris Mason <chris.mason@fusionio.com>,
"open list:BTRFS FILE SYSTEM" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: cleanup redundant code in __btrfs_close_devices()
Date: Tue, 10 Sep 2013 21:15:15 +0800 [thread overview]
Message-ID: <FCA484B4-67E2-4437-A16F-E3FEF751E2C1@gmail.com> (raw)
In-Reply-To: <CAG5DWogv3meJ3-F5QPCGbxtavMrnjjf=-p1KrGNQYao+Nm+pHA@mail.gmail.com>
> On Mon, Sep 9, 2013 at 7:28 AM, Wang Shilong <wangsl.fnst@cn.fujitsu.com> wrote:
>> On 09/08/2013 12:15 AM, Azat Khuzhin wrote:
>>>
>>> Signed-off-by: Azat Khuzhin <a3at.mail@gmail.com>
>>> ---
>>> fs/btrfs/volumes.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>>> index 1d1b595..124228e 100644
>>> --- a/fs/btrfs/volumes.c
>>> +++ b/fs/btrfs/volumes.c
>>> @@ -644,7 +644,7 @@ static int __btrfs_close_devices(struct
>>> btrfs_fs_devices *fs_devices)
>>> /* Safe because we are under uuid_mutex */
>>> if (device->name) {
>>> name = rcu_string_strdup(device->name->str,
>>> GFP_NOFS);
>>> - BUG_ON(device->name && !name); /* -ENOMEM */
>>> + BUG_ON(!name); /* -ENOMEM *
>>
>> Nice catch! out of memory should not trigger BUG_ON()..
>> Maybe we can handle it gracefully.
>
> Maybe return -ENOMEM ?
Yeah, BUG_On is really unfriendly. And here ENOMEM triggers
BUG_ON() is a lazy approach.
I think we can return -ENOMEM rather than BUG_ON(), the caller can handle this.
Thanks,
Wang
>
>>
>> Thanks,
>> Wang
>>
>>> rcu_assign_pointer(new_device->name, name);
>>> }
>>> new_device->bdev = NULL;
>>
>>
>
>
>
> --
> Respectfully
> Azat Khuzhin
> --
> 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:[~2013-09-10 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 16:15 Azat Khuzhin
[not found] ` <522D4061.3060404@cn.fujitsu.com>
2013-09-10 11:39 ` Azat Khuzhin
2013-09-10 13:15 ` Wang Shilong [this message]
2013-09-10 20:40 ` Azat Khuzhin
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=FCA484B4-67E2-4437-A16F-E3FEF751E2C1@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=a3at.mail@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangsl.fnst@cn.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
all inboxes | Powered by JetHome®