From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: fstests <fstests@vger.kernel.org>,
"Misono, Tomohiro" <misono.tomohiro@jp.fujitsu.com>,
linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] fstests: filter mount error message for EUCLEAN and ESTALE
Date: Thu, 23 Nov 2017 17:28:55 +0800 [thread overview]
Message-ID: <20171123092855.GW2749@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAOQ4uxig6TeT62EkHsXFU-2Phstsyd3xiRE5WKmG0hkWu5r5Xw@mail.gmail.com>
On Thu, Nov 23, 2017 at 11:04:57AM +0200, Amir Goldstein wrote:
> On Tue, Nov 14, 2017 at 2:33 PM, Eryu Guan <eguan@redhat.com> wrote:
> > util-linux commit ea848180dd34 ("libmount: add
> > mnt_context_get_excode()") since v2.30 changed the error message on
> > EUCLEAN and ESTALE again (and maybe other errno too):
> >
> > - mount: <device> on <mountpoint> failed: Structure needs cleaning
> > + mount: <mountpoint>: mount(2) system call failed: Structure needs cleaning.
> >
> > and it causes xfs/005, overlay/037 to fail (and probably xfs/333 too,
> > but it's always _notrun for now).
> >
> > So let's filter out the changing parts and keep the error message
> > simple.
> >
> > Signed-off-by: Eryu Guan <eguan@redhat.com>
> > ---
> > common/filter | 23 +++++++++++++++++++++++
> > tests/overlay/037 | 4 ++--
> > tests/overlay/037.out | 4 ++--
> > tests/xfs/005 | 7 +------
> > tests/xfs/333 | 2 +-
> > tests/xfs/333.out | 2 +-
> > 6 files changed, 30 insertions(+), 12 deletions(-)
> >
> > diff --git a/common/filter b/common/filter
> > index 0cb458b0051f..d1bb94818e3d 100644
> > --- a/common/filter
> > +++ b/common/filter
> > @@ -390,6 +390,13 @@ _filter_fstrim()
> > egrep -o "[0-9]+ bytes" | $AWK_PROG '{print $1}'
> > }
> >
> > +# Remove the ending dot appended to mount error message, util-linux 2.30
> > +# starts to do so.
> > +_filter_ending_dot()
> > +{
> > + sed -e "s/\.$//"
> > +}
> > +
> > # Older mount output referred to "block device" when mounting RO devices
> > # It's gone in newer versions
> > _filter_ro_mount() {
> > @@ -397,6 +404,22 @@ _filter_ro_mount() {
> > -e "s/mount: cannot mount block device/mount: cannot mount/g"
> > }
> >
> > +# Filter a failed mount output, util-linux changed the message several times.
> > +#
> > +# prior to v2.21:
> > +# mount: Structure needs cleaning
>
> So the mentioned tests are currently also broken with util-linux < v2.21?
> Maybe mention this is commit message.
Yeah, I think so, just v2.21 is pretty old, the affected tests are
usually _notrun on such old distributions that ship util-linux < v2.21,
e.g. RHEL6, so no one noticed it. I'll mention it in commit log.
>
> > +# v2.21 to v2.29:
> > +# mount: mount <device> on <mountpoint> failed: Structure needs cleaning
> > +# v2.30 and later:
> > +# mount: <mountpoint>: mount(2) system call failed: Structure needs cleaning.
> > +#
>
> Please document filtered format.
OK.
Thanks,
Eryu
next prev parent reply other threads:[~2017-11-23 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 12:33 [PATCH v2 0/3] fix failures caused by mount error msg change in util-linux v2.30 Eryu Guan
2017-11-14 12:33 ` [PATCH v2 1/3] fstests: filter mount error message for EUCLEAN and ESTALE Eryu Guan
2017-11-23 9:04 ` Amir Goldstein
2017-11-23 9:28 ` Eryu Guan [this message]
2017-11-14 12:33 ` [PATCH v2 2/3] overlay/036: filter busy mount message Eryu Guan
2017-11-23 8:57 ` Amir Goldstein
2017-11-14 12:33 ` [PATCH v2 3/3] fstests: filter readonly mount error messages Eryu Guan
2017-11-23 8:32 ` Amir Goldstein
2017-11-23 8:45 ` Eryu Guan
2017-11-23 7:05 ` [PATCH v2 0/3] fix failures caused by mount error msg change in util-linux v2.30 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=20171123092855.GW2749@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=misono.tomohiro@jp.fujitsu.com \
/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).