From: Christoph Hellwig <hch@infradead.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH 0/6] RFC add blkdev tests v2
Date: Thu, 6 Apr 2017 06:55:24 -0700 [thread overview]
Message-ID: <20170406135524.GA12230@infradead.org> (raw)
In-Reply-To: <1491484750-9164-1-git-send-email-dmonakhov@openvz.org>
I still disagree with using xfstests for this. Even if we were going
to treat the block devices nodes as yet another file system that's not
what the patches do - they create specific virtual devices to test
for each test.
I think the right way is to keep your patches as-is and copy the few
bits you use from xfstests into a new repository.
next prev parent reply other threads:[~2017-04-06 13:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 13:19 [PATCH 0/6] RFC add blkdev tests v2 Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 1/6] add lio-target helpers Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 2/6] add: blockdev/001 check page-cache coherency after BLKDISCARD Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 3/6] new: blockdev/002 check information leak for lio-fileio Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 4/6] new: blockdev/003 basic blockdev T10-DIF-TYPE1 integrity checks Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 5/6] new: blockdev/004 Check that live fs survives blkdev page truncation Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 6/6] new: blockdev/005 Check that busy " Dmitry Monakhov
2017-04-06 13:55 ` Christoph Hellwig [this message]
2017-04-06 14:33 ` [PATCH 0/6] RFC add blkdev tests v2 Jens Axboe
2017-04-06 14:47 ` Christoph Hellwig
2017-04-06 14:51 ` Jens Axboe
2017-04-06 15:20 ` Johannes Thumshirn
2017-04-06 15:32 ` Eric Sandeen
2017-04-06 18:15 ` Johannes Thumshirn
2017-04-06 18:19 ` Jens Axboe
2017-04-06 18:22 ` Christoph Hellwig
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=20170406135524.GA12230@infradead.org \
--to=hch@infradead.org \
--cc=dmonakhov@openvz.org \
--cc=fstests@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@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).