From: Eryu Guan <eguan@redhat.com>
To: Hou Tao <houtao1@huawei.com>
Cc: fstests@vger.kernel.org, guaneryu@gmail.com,
linux-xfs@vger.kernel.org, darrick.wong@oracle.com,
cmaiolino@redhat.com
Subject: Re: [PATCH v4 0/4] test for XFS umount hang caused by the pending dquota log item in AIL
Date: Thu, 11 Jan 2018 16:02:42 +0800 [thread overview]
Message-ID: <20180111080242.GI5123@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20180111064933.12088-1-houtao1@huawei.com>
On Thu, Jan 11, 2018 at 02:49:29PM +0800, Hou Tao wrote:
> Hi,
>
> This is the v4 patchset for testing the XFS umount hang problem caused by
> the pending dquota log item in AIL. The problem had been fixed by commit
> 373b058 ("xfs: Properly retry failed dquot items in case of error during
> buffer writeback"). The changes for v4 are appended in the commit log
> of each patches.
>
> Comments and questions are welcome.
The patches all look good, thanks a lot for the revision!
>
> Regards,
> Tao
>
> Hou Tao (4):
> dmflakey: support multiple dm targets for a dm-flakey device
> dmflakey: support error_writes feature for dm-flakey
> xfs: test for umount hang caused by the pending dquota log item in AIL
> common/rc: factor out _scratch_xfs_[get|set]_sb_field
I switched the order of the last two patches, i.e. refactor
_scratch_xfs_[get|set]_sb_field first then use the new helper in the new
test in the end, so we don't add new test then update it again in the
same patch set.
Thanks,
Eryu
>
> common/dmflakey | 31 +++++++++-
> common/fuzzy | 33 -----------
> common/xfs | 47 +++++++++++++++
> tests/xfs/007 | 6 +-
> tests/xfs/098 | 4 +-
> tests/xfs/186 | 3 +-
> tests/xfs/199 | 13 ++--
> tests/xfs/307 | 11 +---
> tests/xfs/308 | 11 +---
> tests/xfs/339 | 6 +-
> tests/xfs/340 | 2 +-
> tests/xfs/999 | 174 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/xfs/999.out | 2 +
> tests/xfs/group | 1 +
> 14 files changed, 269 insertions(+), 75 deletions(-)
> create mode 100755 tests/xfs/999
> create mode 100644 tests/xfs/999.out
>
> --
> 2.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-11 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 6:49 [PATCH v4 0/4] test for XFS umount hang caused by the pending dquota log item in AIL Hou Tao
2018-01-11 6:49 ` [PATCH v4 1/4] dmflakey: support multiple dm targets for a dm-flakey device Hou Tao
2018-01-11 6:49 ` [PATCH v4 2/4] dmflakey: support error_writes feature for dm-flakey Hou Tao
2018-01-11 6:49 ` [PATCH v4 3/4] xfs: test for umount hang caused by the pending dquota log item in AIL Hou Tao
2018-01-11 6:49 ` [PATCH v4 4/4] common/rc: factor out _scratch_xfs_[get|set]_sb_field Hou Tao
2018-01-11 8:02 ` Eryu Guan [this message]
2018-01-11 9:23 ` [PATCH v4 0/4] test for XFS umount hang caused by the pending dquota log item in AIL Hou Tao
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=20180111080242.GI5123@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=houtao1@huawei.com \
--cc=linux-xfs@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