From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 6/6] btrfs: teach print_leaf about temporary item subtypes
Date: Thu, 11 Feb 2016 18:23:45 +0100 [thread overview]
Message-ID: <9f07e1d76eaeeddedcf9651395b4a8f870df31f0.1455209994.git.dsterba@suse.com> (raw)
In-Reply-To: <cover.1455209994.git.dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
---
fs/btrfs/print-tree.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/fs/btrfs/print-tree.c b/fs/btrfs/print-tree.c
index 7bd0bdfc9812..147dc6ca5de1 100644
--- a/fs/btrfs/print-tree.c
+++ b/fs/btrfs/print-tree.c
@@ -306,6 +306,17 @@ void btrfs_print_leaf(struct btrfs_root *root, struct extent_buffer *l)
printk(KERN_INFO "\t\tunknown persistent item\n");
}
break;
+ case BTRFS_TEMPORARY_ITEM_KEY:
+ printk(KERN_INFO "\t\ttemporary item objectid %llu offset %llu\n",
+ key.objectid, key.offset);
+ switch (key.objectid) {
+ case BTRFS_BALANCE_OBJECTID:
+ printk(KERN_INFO "\t\tbalance status\n");
+ break;
+ default:
+ printk(KERN_INFO "\t\tunknown temporary item\n");
+ }
+ break;
case BTRFS_DEV_REPLACE_KEY:
printk(KERN_INFO "\t\tdev replace\n");
break;
--
2.7.1
prev parent reply other threads:[~2016-02-11 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 17:23 [PULL] [PATCH 0/6] B-tree key space extensions David Sterba
2016-02-11 17:23 ` [PATCH 1/6] btrfs: introduce key type for persistent temporary items David Sterba
2016-02-11 17:23 ` [PATCH 2/6] btrfs: switch balance item to the temporary item key David Sterba
2016-02-11 17:23 ` [PATCH 3/6] btrfs: introduce key type for persistent permanent items David Sterba
2016-02-11 17:23 ` [PATCH 4/6] btrfs: switch dev stats item to the permanent item key David Sterba
2016-02-11 17:23 ` [PATCH 5/6] btrfs: teach print_leaf about permanent item subtypes David Sterba
2016-02-11 17:23 ` 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=9f07e1d76eaeeddedcf9651395b4a8f870df31f0.1455209994.git.dsterba@suse.com \
--to=dsterba@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).