From: Eric Sandeen <sandeen@redhat.com>
To: Zach Brown <zab@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 03/12] btrfs: handle errors from reading the quota tree root
Date: Mon, 04 Aug 2014 13:53:08 -0500 [thread overview]
Message-ID: <53DFD694.4070809@redhat.com> (raw)
In-Reply-To: <20140804185113.GC18659@lenny.home.zabbo.net>
On 8/4/14, 1:51 PM, Zach Brown wrote:
> On Mon, Aug 04, 2014 at 01:42:23PM -0500, Eric Sandeen wrote:
>> On 8/4/14, 1:35 PM, Zach Brown wrote:
>>> On Fri, Aug 01, 2014 at 06:12:37PM -0500, Eric Sandeen wrote:
>>>> Reading the quota tree root may fail with ENOENT
>>>> if there is no quota, which is fine, but the code was
>>>> ignoring every other error as well, which is not fine.
>>>
>>> Kinda makes you want to write a test that would have caught this.
>>>
>>> Kinda.
>>
>> /me looks at ground, shuffles feet ...
>>
>>> Also, if you're still keen to iterate on this series, it looks like this
>>> pattern is copied and pasted a few times in open_ctree(). With
>>> temporary root pointers for each block, for some reason. A little
>>> helper function could take a bite out of open_ctree().
>>
>> Hm, the uuid tree is roughly similar, but not exactly. I think those
>> are the only 2 "optional" roots (uuid because it'll get regenerated).
>>
>> I'm guessing the temporary root pointer is so we don't ever assign a
>> PTR_ERR to the root in fs_info?
>
> It took me a while to see what you meant.
>
> Yeah, using a temporary root makes sense. Using a different one for
> each block makes less sense.
>
<snip>
> - z
>
Yeah, fair enough, I thought about that after I hit send ;)
I could send a V2 of patch 11/12 to do that w/o needing to redo
the series too much. :) I'll see if there are any other comments.
Thanks!
-Eric
next prev parent reply other threads:[~2014-08-04 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 23:12 [PATCH 00/12] disk-io.c / open_ctree cleanup & refactoring Eric Sandeen
2014-08-01 23:12 ` [PATCH 01/12] btrfs: remove unused fs_info arg from btrfs_close_extra_devices() Eric Sandeen
2014-08-01 23:12 ` [PATCH 02/12] btrfs: consistently use fs_info in close_ctree() Eric Sandeen
2014-08-01 23:12 ` [PATCH 03/12] btrfs: handle errors from reading the quota tree root Eric Sandeen
2014-08-04 18:35 ` Zach Brown
2014-08-04 18:42 ` Eric Sandeen
2014-08-04 18:51 ` Zach Brown
2014-08-04 18:53 ` Eric Sandeen [this message]
2014-08-01 23:12 ` [PATCH 04/12] btrfs: factor btrfs_scrub_init() out of open_ctree() Eric Sandeen
2014-08-01 23:12 ` [PATCH 05/12] btrfs: factor btrfs_balance_init() " Eric Sandeen
2014-08-01 23:12 ` [PATCH 06/12] btrfs: factor btrfs_btree_inode_init() " Eric Sandeen
2014-08-01 23:12 ` [PATCH 07/12] btrfs: factor btrfs_dev_replace_locks_init() " Eric Sandeen
2014-08-01 23:12 ` [PATCH 08/12] btrfs: factor btrfs_qgroup_init() " Eric Sandeen
2014-08-01 23:12 ` [PATCH 09/12] btrfs: factor btrfs_setup_super() " Eric Sandeen
2014-08-01 23:12 ` [PATCH 10/12] btrfs: factor btrfs_alloc_workqueues() " Eric Sandeen
2014-08-01 23:12 ` [PATCH 11/12] btrfs: factor btrfs_read_roots() " Eric Sandeen
2014-08-01 23:12 ` [PATCH 12/12] btrfs: factor btrfs_replay_log() " Eric Sandeen
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=53DFD694.4070809@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.