linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [patch 9/9] btrfs: Push up non-looped btrfs_start_transaction failures
Date: Wed, 10 Aug 2011 21:58:00 -0400	[thread overview]
Message-ID: <4E433728.8060406@suse.com> (raw)
In-Reply-To: <4E433013.3010600@jp.fujitsu.com>

On 08/10/2011 09:27 PM, Tsutomu Itoh wrote:
> Hi, Jeff,
> 
> (2011/08/11 8:20), Jeff Mahoney wrote:
>>   This patch handles btrfs_start_transaction failures that don't occur
>>   in a loop and are obvious to simply push up. In all cases except the
>>   mark_garbage_root case, the error is already handled by BUG_ON in the
>>   caller.
>>
>> Signed-off-by: Jeff Mahoney<jeffm@suse.com>
>> ---
>>   fs/btrfs/extent-tree.c |    6 +++++-
>>   fs/btrfs/relocation.c  |    6 ++++--
>>   fs/btrfs/tree-log.c    |    5 ++++-
>>   fs/btrfs/volumes.c     |    3 ++-
>>   4 files changed, 15 insertions(+), 5 deletions(-)
>>
>> --- a/fs/btrfs/extent-tree.c
>> +++ b/fs/btrfs/extent-tree.c
>> @@ -6319,7 +6319,11 @@ int btrfs_drop_snapshot(struct btrfs_roo
>>   	}
>>
>>   	trans = btrfs_start_transaction(tree_root, 0);
>> -	BUG_ON(IS_ERR(trans));
>> +	if (IS_ERR(trans)) {
>> +		kfree(wc);
>> +		btrfs_free_path(path);
>> +		return PTR_ERR(trans);
>> +	}
> 
> The caller of btrfs_drop_snapshot() ignore the error. So, I don't think
> that it is significant even if the error is returned to the caller.

 I'd actually consider that a separate issue since btrfs_drop_snapshot
also returns -ENOMEM. The errors should be properly caught or BUG_ON'd
in the caller. My patchset usually catches cases like this but since
btrfs_drop_snapshot already returned an error, I mistakenly assumed it
was handled by the caller.

> I think that it should make the filesystem readonly when becoming an error
> in btrfs_start_transaction().

For -ENOMEM, I don't think that's the way to handle it. Some transaction
start failures can be caught and handled (e.g. just creating a file)
easily by returning errors to the user. Other cases, deep in the code,
may be too complex to unwind and recover from and then a ROFS is the
next-best answer. The callers should be responsible for determining the
correct course of action.

-Jeff

> Thanks,
> Tsutomu
> 
>>
>>   	if (block_rsv)
>>   		trans->block_rsv = block_rsv;
>> --- a/fs/btrfs/relocation.c
>> +++ b/fs/btrfs/relocation.c
>> @@ -4096,7 +4096,8 @@ static noinline_for_stack int mark_garba
>>   	int ret;
>>
>>   	trans = btrfs_start_transaction(root->fs_info->tree_root, 0);
>> -	BUG_ON(IS_ERR(trans));
>> +	if (IS_ERR(trans))
>> +		return PTR_ERR(trans);
>>
>>   	memset(&root->root_item.drop_progress, 0,
>>   		sizeof(root->root_item.drop_progress));
>> @@ -4176,7 +4177,8 @@ int btrfs_recover_relocation(struct btrf
>>   					err = ret;
>>   					goto out;
>>   				}
>> -				mark_garbage_root(reloc_root);
>> +				ret = mark_garbage_root(reloc_root);
>> +				BUG_ON(ret);
>>   			}
>>   		}
>>
>> --- a/fs/btrfs/tree-log.c
>> +++ b/fs/btrfs/tree-log.c
>> @@ -3151,7 +3151,10 @@ int btrfs_recover_log_trees(struct btrfs
>>   	fs_info->log_root_recovering = 1;
>>
>>   	trans = btrfs_start_transaction(fs_info->tree_root, 0);
>> -	BUG_ON(IS_ERR(trans));
>> +	if (IS_ERR(trans)) {
>> +		btrfs_free_path(path);
>> +		return PTR_ERR(trans);
>> +	}
>>
>>   	wc.trans = trans;
>>   	wc.pin = 1;
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -1876,7 +1876,8 @@ static int btrfs_relocate_chunk(struct b
>>   		return ret;
>>
>>   	trans = btrfs_start_transaction(root, 0);
>> -	BUG_ON(IS_ERR(trans));
>> +	if (IS_ERR(trans))
>> +		return PTR_ERR(trans);
>>
>>   	lock_chunks(root);
>>
> 


-- 
Jeff Mahoney
SuSE Labs

  reply	other threads:[~2011-08-11  1:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 23:20 [patch 0/9] btrfs: More error handling patches Jeff Mahoney
2011-08-10 23:20 ` [patch 1/9] btrfs: Add btrfs_panic() Jeff Mahoney
2011-08-10 23:20 ` [patch 2/9] btrfs: Catch locking failures in {set,clear}_extent_bit Jeff Mahoney
2011-08-10 23:20 ` [patch 3/9] btrfs: Push up set_extent_bit errors to callers Jeff Mahoney
2011-08-11  0:08   ` Jeff Mahoney
2011-08-10 23:20 ` [patch 4/9] btrfs: Push up lock_extent " Jeff Mahoney
2011-08-10 23:20 ` [patch 5/9] btrfs: Push up clear_extent_bit " Jeff Mahoney
2011-08-10 23:20 ` [patch 6/9] btrfs: Push up unlock_extent " Jeff Mahoney
2011-08-10 23:20 ` [patch 7/9] btrfs: Make pin_down_extent return void Jeff Mahoney
2011-08-10 23:20 ` [patch 8/9] btrfs: Push up btrfs_pin_extent failures Jeff Mahoney
2011-08-10 23:20 ` [patch 9/9] btrfs: Push up non-looped btrfs_start_transaction failures Jeff Mahoney
2011-08-11  1:27   ` Tsutomu Itoh
2011-08-11  1:58     ` Jeff Mahoney [this message]
2011-08-11  2:18       ` Tsutomu Itoh
2011-08-11  2:32         ` Jeff Mahoney

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=4E433728.8060406@suse.com \
    --to=jeffm@suse.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).