From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/3] Cleanups in mount path
Date: Thu, 10 Oct 2019 18:06:44 +0300 [thread overview]
Message-ID: <20191010150647.20940-1-nborisov@suse.com> (raw)
Following the misunderstanding around the 2nd argument of free_root_pointers it
became apparent that the relevant code in open_ctre is not entirely clear. That's
mainly due it being split among 2 labels, emulating a loop. This series
cleans that up by factoring it out in a discrete function, init_root_trees in
patch 1 and then subsequent patches implement minor cleanups that became
apparent while working with the code.
This has survived full xfstest run.
Nikolay Borisov (3):
btrfs: Factor out tree roots initialization during mount
btrfs: Don't use objectid_mutex during mount
btrfs: Jump to correct label on init_root_trees failure
fs/btrfs/disk-io.c | 138 +++++++++++++++++++++++++--------------------
1 file changed, 78 insertions(+), 60 deletions(-)
--
2.17.1
next reply other threads:[~2019-10-10 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:06 Nikolay Borisov [this message]
2019-10-10 15:06 ` [PATCH 1/3] btrfs: Factor out tree roots initialization during mount Nikolay Borisov
2019-10-11 7:50 ` Johannes Thumshirn
2019-10-11 8:21 ` Nikolay Borisov
2019-10-11 8:23 ` Johannes Thumshirn
2019-10-11 9:31 ` Qu Wenruo
2019-10-11 10:12 ` Nikolay Borisov
2019-10-10 15:06 ` [PATCH 2/3] btrfs: Don't use objectid_mutex " Nikolay Borisov
2019-10-10 16:05 ` David Sterba
2019-10-10 15:06 ` [PATCH 3/3] btrfs: Jump to correct label on init_root_trees failure Nikolay Borisov
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=20191010150647.20940-1-nborisov@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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).