From: Eryu Guan <eguan@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Andreas Dilger <adilger@dilger.ca>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
fstests@vger.kernel.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH xfstests] dirstress: Allow ESTALE as well as ENOENT
Date: Fri, 25 Nov 2016 19:35:11 +0800 [thread overview]
Message-ID: <20161125113511.GI4609@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20161125034706.GA20729@fieldses.org>
Hi Bruce,
On Thu, Nov 24, 2016 at 10:47:06PM -0500, J. Bruce Fields wrote:
> On Wed, Nov 23, 2016 at 04:19:11PM -0700, Andreas Dilger wrote:
> > On Nov 23, 2016, at 3:20 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > >
> > > From: "J. Bruce Fields" <bfields@redhat.com>
> > >
> > > In the NFS case an attempt to chdir out of a removed directory could result
> > > in ESTALE, and that should not cause the test to fail.
> > >
> > > This was causing intermittent failures on generic/011 on NFS.
> > >
> > > Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> > > ---
> > > src/dirstress.c | 12 ++++++++----
> > > 1 file changed, 8 insertions(+), 4 deletions(-)
> > >
> > > Sorry, who do xfstests patches go to?--b.
> >
> > They are sent to fstests@vger.kernel.org
>
> Thanks!
>
> Might be worth something like this too?
This looks fine to me. Can you please resend as a formal patch? Also the
patch to fix dirstress.c.
Thanks,
Eryu
next prev parent reply other threads:[~2016-11-25 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 22:20 [PATCH xfstests] dirstress: Allow ESTALE as well as ENOENT J. Bruce Fields
2016-11-23 23:19 ` Andreas Dilger
2016-11-25 3:47 ` J. Bruce Fields
2016-11-25 11:35 ` Eryu Guan [this message]
2016-11-26 1:39 ` [PATCH 1/2] Document fstests mailing list J. Bruce Fields
2016-11-26 1:39 ` [PATCH 2/2] dirstress: Allow ESTALE as well as ENOENT J. Bruce Fields
2016-11-29 6:43 ` Eryu Guan
2016-11-29 14:34 ` J. Bruce Fields
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=20161125113511.GI4609@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=adilger@dilger.ca \
--cc=bfields@fieldses.org \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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).