From: Eryu Guan <eguan@redhat.com>
To: Filipe Manana <fdmanana@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] common: make sure dm error device is all settled before removing it
Date: Thu, 24 Mar 2016 21:17:22 +0800 [thread overview]
Message-ID: <20160324131722.GV11419@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAL3q7H47cu7zwu43TzZ=VyzVYrY8U5HGPR_pmNfk_HkQ3hyUCg@mail.gmail.com>
On Thu, Mar 24, 2016 at 12:34:55PM +0000, Filipe Manana wrote:
> On Thu, Mar 24, 2016 at 12:08 PM, Eryu Guan <eguan@redhat.com> wrote:
> > _dmerror_cleanup() may fail to remove error-test device due to EBUSY and
> > cause subsequent tests to fail.
> >
> > Fix it by calling $UDEV_SETTLE_PROG before remove error-test device to
> > make sure no one is using it.
>
> I often get the same problem with _cleanup_flakey.
> Would you be doing the same for flakey in this or another patch?
I'm going to fix them in one patch.
>
> >
> > Signed-off-by: Eryu Guan <eguan@redhat.com>
>
> Reviewed-by: Filipe Manana <fdmanana@suse.com>
Thanks!
Eryu
>
> > ---
> > common/dmerror | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/common/dmerror b/common/dmerror
> > index 004530d..5d2c1b6 100644
> > --- a/common/dmerror
> > +++ b/common/dmerror
> > @@ -54,6 +54,9 @@ _dmerror_unmount()
> > _dmerror_cleanup()
> > {
> > $UMOUNT_PROG $SCRATCH_MNT > /dev/null 2>&1
> > + # wait for device to be fully settled so that 'dmsetup remove' doesn't
> > + # fail due to EBUSY
> > + $UDEV_SETTLE_PROG >/dev/null 2>&1
> > $DMSETUP_PROG remove error-test > /dev/null 2>&1
> > }
> >
> > --
> > 2.5.5
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe fstests" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> Filipe David Manana,
>
> "Reasonable men adapt themselves to the world.
> Unreasonable men adapt the world to themselves.
> That's why all progress depends on unreasonable men."
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" 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:[~2016-03-24 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 12:08 [PATCH] common: make sure dm error device is all settled before removing it Eryu Guan
2016-03-24 12:34 ` Filipe Manana
2016-03-24 13:17 ` Eryu Guan [this message]
2016-03-24 13:25 ` [PATCH v2] common: make sure dm " Eryu Guan
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=20160324131722.GV11419@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fdmanana@gmail.com \
--cc=fstests@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