From: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH RESEND 0/4] fix alert and add testcase lowmem check
Date: Fri, 3 Nov 2017 16:28:02 +0800 [thread overview]
Message-ID: <20171103082806.22448-1-lufq.fnst@cn.fujitsu.com> (raw)
Patch 1 add a test case for commit 4c75ae7a4e20 ("btrfs-progs: test: Add
test image for lowmem mode file extent interrupt")
Patch 2 output more detailed information about file extent interrupt
Patch 3 fix a false alert for lowmem check
Patch 4 add a test case for Patch 3
Lu Fengqi (4):
btrfs-progs: test: Add test image for lowmem mode file extent
interrupt
btrfs-progs: lowmem check: Output more detailed information about file
extent interrupt
btrfs-progs: lowmem check: Fix false alert about referencer count
mismatch
btrfs-progs: test: Add test image for lowmem mode referencer count
mismatch false alert
cmds-check.c | 8 +++++---
.../020-extent-ref-cases/inline_regular_coexist.img | Bin 0 -> 4096 bytes
.../ref_count_mismatch_false_alert.img | Bin 0 -> 4096 bytes
3 files changed, 5 insertions(+), 3 deletions(-)
create mode 100644 tests/fsck-tests/020-extent-ref-cases/inline_regular_coexist.img
create mode 100644 tests/fsck-tests/020-extent-ref-cases/ref_count_mismatch_false_alert.img
--
2.15.0
next reply other threads:[~2017-11-03 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 8:28 Lu Fengqi [this message]
2017-11-03 8:28 ` [PATCH RESEND 1/4] btrfs-progs: test: Add test image for lowmem mode file extent interrupt Lu Fengqi
2017-11-03 8:28 ` [PATCH RESEND 2/4] btrfs-progs: lowmem check: Output more detailed information about " Lu Fengqi
2017-11-03 8:28 ` [PATCH RESEND 3/4] btrfs-progs: lowmem check: Fix false alert about referencer count mismatch Lu Fengqi
2017-11-03 8:28 ` [PATCH RESEND 4/4] btrfs-progs: test: Add test image for lowmem mode referencer count mismatch false alert Lu Fengqi
2017-11-09 16:23 ` [PATCH RESEND 0/4] fix alert and add testcase lowmem check David Sterba
2017-11-09 16:25 ` 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=20171103082806.22448-1-lufq.fnst@cn.fujitsu.com \
--to=lufq.fnst@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 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).