From: David Sterba <dave@jikos.cz>
To: Wang Sheng-Hui <shhuiw@gmail.com>
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] btrfs: remove unnecessary -ENOMEM BUG_ON check in extent-tree.c/btrfs_alloc_logged_file_extent
Date: Thu, 6 Sep 2012 12:19:30 +0200 [thread overview]
Message-ID: <20120906101930.GP17430@twin.jikos.cz> (raw)
In-Reply-To: <5048457E.6050002@gmail.com>
On Thu, Sep 06, 2012 at 02:41:02PM +0800, Wang Sheng-Hui wrote:
> The memory allocation failure is BUG_ON in add_excluded_extent
> (following the code path). No need to BUG_ON -ENOMEM inside
> btrfs_alloc_logged_file_extent.
This indirectly calls __set_extent_bit that does BUG_ON on memory
allocation failures. This type of error condition is hard to fix, as it
usually needs to do non-trivial cleanups in the function before
returning -ENOMEM, so the easiset way to "handle" it is to do BUG_ON and
then separately deal with it in another patch (so it does not mix with
the original patch).
Your patches remove (from my POV) useful marks that we have an error
condition to handle, not to hide it.
So, NAK from me for anything that looks like this. I'm of course glad to
look at patches that replace the BUG_ON with proper error handling :)
david
>
> Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
> ---
> fs/btrfs/extent-tree.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 95492cc..9b9a6fa 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -6207,8 +6207,7 @@ int btrfs_alloc_logged_file_extent(struct btrfs_trans_handle *trans,
> mutex_lock(&caching_ctl->mutex);
>
> if (start >= caching_ctl->progress) {
> - ret = add_excluded_extent(root, start, num_bytes);
> - BUG_ON(ret); /* -ENOMEM */
> + add_excluded_extent(root, start, num_bytes);
> } else if (start + num_bytes <= caching_ctl->progress) {
> ret = btrfs_remove_free_space(block_group,
> start, num_bytes);
> @@ -6222,8 +6221,7 @@ int btrfs_alloc_logged_file_extent(struct btrfs_trans_handle *trans,
> start = caching_ctl->progress;
> num_bytes = ins->objectid + ins->offset -
> caching_ctl->progress;
> - ret = add_excluded_extent(root, start, num_bytes);
> - BUG_ON(ret); /* -ENOMEM */
> + add_excluded_extent(root, start, num_bytes);
> }
>
> mutex_unlock(&caching_ctl->mutex);
prev parent reply other threads:[~2012-09-06 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 6:41 [PATCH 2/3] btrfs: remove unnecessary -ENOMEM BUG_ON check in extent-tree.c/btrfs_alloc_logged_file_extent Wang Sheng-Hui
2012-09-06 10:19 ` David Sterba [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=20120906101930.GP17430@twin.jikos.cz \
--to=dave@jikos.cz \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shhuiw@gmail.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