From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH 0/5] libbtrfsutil: misc fixes
Date: Thu, 29 Mar 2018 00:53:52 -0700 [thread overview]
Message-ID: <cover.1522309741.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi, Dave,
This is a handful of minor fixes for libbtrfsutil that would be good to
get in before the release. Patch 1 fixes an issue reported by Tomohiro a
few weeks back. Patch 2 fixes a memory leak I noticed while writing
patch 1. Patch 3 makes us use the local mkfs.btrfs so that the tests can
run on the CI system. Patch 4 fixes an issue I noticed while testing
that fix. Patch 5 fixes a test failure caused by "btrfs-progs: mkfs: add
uuid and otime to ROOT_ITEM of, FS_TREE".
Based on your devel branch. Please apply!
Omar Sandoval (5):
libbtrfsutil: don't return free space cache inodes from
deleted_subvolumes()
libbtrfsutil: fix memory leak in deleted_subvolumes()
libbtrfsutil: use local mkfs.btrfs for tests if it exists
libbtrfsutil: always build libbtrfsutil.so.$MAJOR
libbtrfsutil: fix test assumptions about top-level subvolume
Makefile | 4 ++--
libbtrfsutil/python/tests/__init__.py | 6 ++++-
libbtrfsutil/python/tests/test_subvolume.py | 8 ++++---
libbtrfsutil/subvolume.c | 34 +++++++++++++++++++----------
4 files changed, 35 insertions(+), 17 deletions(-)
--
2.16.3
next reply other threads:[~2018-03-29 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 7:53 Omar Sandoval [this message]
2018-03-29 7:53 ` [PATCH 1/5] libbtrfsutil: don't return free space cache inodes from deleted_subvolumes() Omar Sandoval
2018-03-29 7:53 ` [PATCH 2/5] libbtrfsutil: fix memory leak in deleted_subvolumes() Omar Sandoval
2018-03-29 7:53 ` [PATCH 3/5] libbtrfsutil: use local mkfs.btrfs for tests if it exists Omar Sandoval
2018-03-29 7:53 ` [PATCH 4/5] libbtrfsutil: always build libbtrfsutil.so.$MAJOR Omar Sandoval
2018-03-29 7:53 ` [PATCH 5/5] libbtrfsutil: fix test assumptions about top-level subvolume Omar Sandoval
2018-03-30 7:39 ` Misono Tomohiro
2018-03-30 21:58 ` [PATCH 0/5] libbtrfsutil: misc fixes 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=cover.1522309741.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.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.