mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: dai.ngo@oracle.com
To: "Jie Zhou (Fujitsu)" <zhoujie2011@fujitsu.com>,
	"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@kernel.org>,
	"Mora, Jorge" <Jorge.Mora@netapp.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: "[PATCH] nfsd: rework refcounting in filecache" caused nfstest/test/nfstest_delegation stuck
Date: Thu, 27 Apr 2023 00:26:44 -0700	[thread overview]
Message-ID: <4a2a77e8-857a-9ca7-5594-15d1004e7d9a@oracle.com> (raw)
In-Reply-To: <6e287adf-25bb-3c62-c390-e642488aaf5c@fujitsu.com>

This problem is fixed in nfsd-next with this commit:

119437271d94 NFSD: Fix problem of COMMIT and NFS4ERR_DELAY in infinite loop

-Dai

On 4/26/23 8:50 PM, Jie Zhou (Fujitsu) wrote:
> hi,
>
>      Download nfstest program from
> "http://git.linux-nfs.org/?p=mora/nfstest.git;a=summary".
>      And run following test command and stuck at recall12 recall14
> recall20 recall22 recall40 recall42 recall48 recall50.
>      ./nfstest_delegation --nfsversion=4.0 -e /nfsroot --server <server
> ip> --client <client2 ip> --trcdelay 10
>      test OS: RHEL9.2 Nightly Build
>
>      After I bisect linux kerenl, found that following patch caused above
> bug.
>   From ac3a2585f018f10039b4a856dcb122da88c1c1c9 Mon Sep 17 00:00:00 2001
> From: Jeff Layton <jlayton@kernel.org>
> Date: Sun, 11 Dec 2022 06:19:33 -0500
> Subject: [PATCH] nfsd: rework refcounting in filecache
>
>      Run following command at different kernel version.
> ./nfstest_delegation --nfsversion=4.0 -e /nfsroot --server
> 192.168.122.153 --client 192.168.122.152 --trcdelay 10 -v all
> --createlog --keeptraces --rexeclog recall22
>   >nfstest-delegationv4-log_recall22 2>&1
>
>      The following test result are attached.
>      kernel:
> commit 0cfd8703e7da687924371e9bc77a025bdeba9637
> Merge: 793582ff47f8 d3f2c402e448
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Tue Apr 25 18:44:10 2023 -0700
>       Merge tag 'pm-6.4-rc1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
>      result:
> test program stuck
>      log:
> nfstest-delegationv4-log_recall22_6.3.0
>
>      kernel:
> commit ac3a2585f018f10039b4a856dcb122da88c1c1c9
> Author: Jeff Layton <jlayton@kernel.org>
> Date:   Sun Dec 11 06:19:33 2022 -0500
>       nfsd: rework refcounting in filecache
>      result:
> test program stuck
>      log:
> nfstest-delegationv4-log_recall22_ac3a2585f018
>
>      kernel:
> commit e78e274eb22d966258a3845acc71d3c5b8ee2ea8
> Author: Kees Cook <keescook@chromium.org>
> Date:   Fri Dec 2 12:48:59 2022 -0800
>       NFSD: Avoid clashing function prototypes
>      result:
> test program stop normally
>      log:
> nfstest-delegationv4-log_recall22_e78e274eb22d
>
> best regards,

      reply	other threads:[~2023-04-27  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  3:50 Jie Zhou (Fujitsu)
2023-04-27  7:26 ` dai.ngo [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=4a2a77e8-857a-9ca7-5594-15d1004e7d9a@oracle.com \
    --to=dai.ngo@oracle.com \
    --cc=Jorge.Mora@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=zhoujie2011@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

all inboxes | Powered by JetHome®