archive mirror
 help / color / mirror / Atom feed
From: Rohith Surabattula <>
To: Murphy Zhou <>
Cc: linux-cifs <>,
	Rohith Surabattula <>
Subject: Re: [regression] lock test hang since 5.13-rc-smb3-part2
Date: Mon, 6 Sep 2021 21:17:31 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Can you please share the mount options.

Did you observe the same failure with 5.14-rc5-smb3-fixes ?
I ran the generic/478 test on 5.14 and didn't see any hang. But, test
fails with below

generic/478     - output mismatch (see
    --- tests/generic/478.out   2021-05-03 19:01:04.767577557 +0000
    +++ /home/lxsmbadmin/xfstests-dev/results//smb3/generic/478.out.bad
              06 15:39:39.625248615 +0000
    @@ -1,13 +1,13 @@
     QA output created by 478
     get wrlck
     lock could be placed
    -get wrlck
    -get wrlck
     lock could be placed
     get wrlck
    (Run 'diff -u /home/lxsmbadmin/xfstests-dev/tests/generic/478.out
 to see the entire diff)
Ran: generic/478
Failures: generic/478
Failed 1 of 1 tests


On Mon, Sep 6, 2021 at 5:16 PM Murphy Zhou <> wrote:
> Hi,
> Since this commit:
> commit c3f207ab29f793b8c942ce8067ed123f18d5b81b
> Author: Rohith Surabattula <>
> Date:   Tue Apr 13 00:26:42 2021 -0500
>     cifs: Deferred close for files
> Xfstests generic/478 on CIFS can't finish like before. The test programme
> never returns but killable. The kernel does not warn about soft or hard
> lockups. So it looks like looping forever at some point.
> It's always reproducible. Without this commit, generic/478 fails the test
> because of different lock schema but complete very fast. With this commit,
> test hang like forever.
> Sorry that I do not look further here, because I have another bisecting to
> do to hunting another regression.
> Thanks,
> Murphy

  reply	other threads:[~2021-09-06 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 11:45 [regression] lock test hang since 5.13-rc-smb3-part2 Murphy Zhou
2021-09-06 15:47 ` Rohith Surabattula [this message]
2021-09-07  3:18   ` Murphy Zhou

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).