public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Josef Bacik <jbacik@fb.com>, Christoph Hellwig <hch@lst.de>,
	fstests <fstests@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Eryu Guan <eguan@redhat.com>
Subject: Re: [RFC][PATCH 7/8] fstests: add support for working with dm-log-writes target
Date: Wed, 23 Aug 2017 12:51:29 -0400	[thread overview]
Message-ID: <20170823165128.fhhjec4ofd4q2u2e@destiny> (raw)
In-Reply-To: <CAOQ4uxiq=b0SeSK17_6d_uPw8owbyNQkkeTiPBUwaVYHpMgQGQ@mail.gmail.com>

On Wed, Aug 23, 2017 at 06:58:38PM +0300, Amir Goldstein wrote:
> On Wed, Aug 23, 2017 at 6:49 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> > Cherry-picked the relevant common bits from commit 70d41e17164b
> > in Josef Bacik's fstests tree (https://github.com/josefbacik/fstests).
> > Quoting from Josef's commit message:
> >
> >   This patch adds the supporting code for using the dm-log-writes
> >   target.  The dmlogwrites code is similar to the dmflakey code, it just
> >   gives us functions to build and tear down a dm-log-writes target.  We
> >   add a new LOGWRITES_DEV variable to take in the device we will use as
> >   the log and add checks for that.
> >
> > [Amir:]
> > - Removed unneeded _test_falloc_support
> > - Moved _require_log_writes to dmlogwrites
> > - Document _require_log_writes
> >
> > Cc: Josef Bacik <jbacik@fb.com>
> > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > ---
> >  README                       |  2 ++
> >  common/dmlogwrites           | 86 ++++++++++++++++++++++++++++++++++++++++++++
> >  doc/requirement-checking.txt | 20 +++++++++++
> >  3 files changed, 108 insertions(+)
> >  create mode 100644 common/dmlogwrites
> >
> 
> ...
> 
> > +
> > +_init_log_writes()
> > +{
> > +       local BLK_DEV_SIZE=`blockdev --getsz $SCRATCH_DEV`
> > +       LOGWRITES_NAME=logwrites-test
> > +       LOGWRITES_DMDEV=/dev/mapper/$LOGWRITES_NAME
> > +       LOGWRITES_TABLE="0 $BLK_DEV_SIZE log-writes $SCRATCH_DEV $LOGWRITES_DEV"
> > +       $DMSETUP_PROG create $LOGWRITES_NAME --table "$LOGWRITES_TABLE" || \
> > +               _fatal "failed to create log-writes device"
> > +       $DMSETUP_PROG mknodes > /dev/null 2>&1
> > +}
> > +
> ...
> > +_cleanup_log_writes()
> > +{
> > +       # If dmsetup load fails then we need to make sure to do resume here
> > +       # otherwise the umount will hang
> 
> Josef,
> 
> Care to explain this comment?
> What do you mean by "resume" here? is this a real concern?
>

I don't know, I think I had this weird suspend/resume thing before but got rid
of it and forgot to remove the comment.  Thanks,

Josef 

  reply	other threads:[~2017-08-23 16:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 15:49 [RFC][PATCH 0/8] Crash consistency xfstest using dm-log-writes Amir Goldstein
2017-08-23 15:49 ` [RFC][PATCH 1/8] common/rc: convert some egrep to grep Amir Goldstein
2017-08-23 15:49 ` [RFC][PATCH 2/8] common/rc: fix _require_xfs_io_command params check Amir Goldstein
2017-08-23 15:49 ` [RFC][PATCH 3/8] fsx: fixes to random seed Amir Goldstein
2017-08-25  9:19   ` Amir Goldstein
2017-08-30  7:00     ` Eryu Guan
2017-08-23 15:49 ` [RFC][PATCH 4/8] fsx: fix path of .fsx* files Amir Goldstein
2017-08-23 15:49 ` [RFC][PATCH 5/8] fsx: add support for integrity check with dm-log-writes target Amir Goldstein
2017-08-23 15:49 ` [RFC][PATCH 6/8] log-writes: add replay-log program to replay " Amir Goldstein
2017-08-23 15:49 ` [RFC][PATCH 7/8] fstests: add support for working with " Amir Goldstein
2017-08-23 15:58   ` Amir Goldstein
2017-08-23 16:51     ` Josef Bacik [this message]
2017-08-23 15:49 ` [RFC][PATCH 8/8] fstests: add crash consistency fsx test using dm-log-writes Amir Goldstein

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=20170823165128.fhhjec4ofd4q2u2e@destiny \
    --to=josef@toxicpanda.com \
    --cc=amir73il@gmail.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=jbacik@fb.com \
    --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