From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Hang in xfstest
Date: Mon, 8 Apr 2024 21:56:58 -0500 [thread overview]
Message-ID: <CAH2r5mtNZT-zvPjxgqKak5uA6pwyAbvEjOmTB24Vg5O_2-91cw@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5muOk9hfCqMzRKnKR3sXOOauGdjbvuzms_bKM+U0t5zihA@mail.gmail.com>
On a more cheerful note - although we do have a regression to fix
here, since 6.4 we have fixed A LOT of things, and lots of
improvements.
As some examples: xfstests generic/075, generic/112 and intermittent
failures in generic/047 and generic/049 which used to fail, now pass,
and multiple tests have been added to the "buildbot" regression
testing automation.
And in the future it looks like we will catch these earlier. If
anyone has regression tests for bugs that have been fixed over the
past few years (that aren't already covered by xfstests), I would be
happy to add them to our regression testing bucket of tests we run
regularly against various server types.
On Mon, Apr 8, 2024 at 5:31 PM Steve French <smfrench@gmail.com> wrote:
>
> I narrowed down (bisected) the cause of the crash in unmount
> generic/046 (to Windows) which causes the hang on following tests
> (generic/047 etc). See
> http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/3/builds/61/steps/73/logs/stdio
> as an example.
>
> The regression started when I add the patch from 6.5-rc1 "cifs: Add a
> laundromat thread for cached directories"
>
> The workaround is to simply disable directory caching for that mount -
> ie "nohandlecache" mount parameter. This unmount race is only an
> issue to servers which support directory leases (e.g. Windows).
>
>
>
>
> --
> Thanks,
>
> Steve
--
Thanks,
Steve
prev parent reply other threads:[~2024-04-09 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 22:31 Hang in xfstest Steve French
2024-04-09 2:56 ` Steve French [this message]
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=CAH2r5mtNZT-zvPjxgqKak5uA6pwyAbvEjOmTB24Vg5O_2-91cw@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs@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 read-only IMAP folder(s) and NNTP newsgroup(s).