From: "Theodore Ts'o" <tytso@mit.edu>
To: Eryu Guan <eguan@redhat.com>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/135: fix standard error output from _scratch_mkfs
Date: Mon, 22 Feb 2016 22:32:49 -0500 [thread overview]
Message-ID: <20160223033249.GH1215@thunk.org> (raw)
In-Reply-To: <20160223032652.GC11419@eguan.usersys.redhat.com>
On Tue, Feb 23, 2016 at 11:26:52AM +0800, Eryu Guan wrote:
> On Tue, Feb 23, 2016 at 09:35:25AM +0800, Xiao Yang wrote:
> > 'mke2fs 1.42.9 (28-Dec-2013)' produces as standard error when
> > we run generic/135 in ext4 file system. This is a regression
> > bug which bring in by commit:
> > 4a5cda8 xfstests: do not unmount tmpfs during remount
> > That patch remove '2>&1', so i bring that back.
>
> Thanks for the revision! But I noticed that Ted's patch fixed it too,
>
> "common: filter warning messages from mkfs.ext4"
>
> which filters the warnings in _scratch_mkfs_ext4, so that other mkfs
> errors can be noticed in the test. So I think it's a better fix :)
Yes, I had revised patch that added the 2>&1 but that wasn't the one
that ended up xfstests repository. I started with a patch to add it
back that looked much like yours (except I used '2>&1' instead of '>&'),
but I started thinking about the fact that this would cause errors to
be masked which is not cool.
I believe Dave or Cristoph has said that they don't like redirecting
stderr to /dev/null for _scratch_mount, and it seems to me that
assuming my change makes it in, it would probably be good to get rid
of the other stderr redirections to /dev/null.
- Ted
next prev parent reply other threads:[~2016-02-23 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 1:35 [PATCH] generic/135: fix standard error output from _scratch_mkfs Xiao Yang
2016-02-23 3:26 ` Eryu Guan
2016-02-23 3:32 ` Theodore Ts'o [this message]
2016-03-02 5:45 ` Xiao Yang
[not found] <CADVQ27rD6UX7eechDFxke7aE=ty3NJJJKtKGsDR2sCVR5=EP=w@mail.gmail.com>
2016-02-22 9:40 ` Zirong Lang
2016-02-22 10:08 ` Xiao Yang
-- strict thread matches above, loose matches on Subject: below --
2016-02-19 13:46 Xiao Yang
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=20160223033249.GH1215@thunk.org \
--to=tytso@mit.edu \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=yangx.jy@cn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.