All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH 0/4] Convert regression fix with print-tree enhancement
Date: Fri, 19 Aug 2016 16:13:04 +0800	[thread overview]
Message-ID: <20160819081308.21348-1-quwenruo@cn.fujitsu.com> (raw)

This patchset fixes one convert regression, adds regression test.
Then with 2 print-tree enhancement, which is quite handy to find how inode
and subvolume READONLY flag is set.

Qu Wenruo (4):
  btrfs-progs: convert: Fix a regression that ext2_save/image is not
    readonly
  btrfs-progs: convert-test: Check if the ext2_save/image is read only
  btrfs-progs: print-tree: Print human readable inode flags
  btrfs-progs: print-tree: Print hex and human readable root flags

 btrfs-convert.c                                |  9 ++++-
 ctree.h                                        |  2 ++
 inode.c                                        | 36 +++++++++++++++++++
 print-tree.c                                   | 49 ++++++++++++++++++++++++--
 tests/convert-tests/008-readonly-image/test.sh | 26 ++++++++++++++
 5 files changed, 119 insertions(+), 3 deletions(-)
 create mode 100755 tests/convert-tests/008-readonly-image/test.sh

-- 
2.9.3




             reply	other threads:[~2016-08-19  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  8:13 Qu Wenruo [this message]
2016-08-19  8:13 ` [PATCH 1/4] btrfs-progs: convert: Fix a regression that ext2_save/image is not readonly Qu Wenruo
2016-08-19  8:13 ` [PATCH 2/4] btrfs-progs: convert-test: Check if the ext2_save/image is read only Qu Wenruo
2016-08-19  8:13 ` [PATCH 3/4] btrfs-progs: print-tree: Print human readable inode flags Qu Wenruo
2016-08-19  8:13 ` [PATCH 4/4] btrfs-progs: print-tree: Print hex and human readable root flags Qu Wenruo
2016-08-19 11:55 ` [PATCH 0/4] Convert regression fix with print-tree enhancement David Sterba

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=20160819081308.21348-1-quwenruo@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.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 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.