FS/XFS testing framework
 help / color / mirror / Atom feed
From: Chengguang Xu <cgxu519@mykernel.net>
To: "cgxu519" <cgxu519@mykernel.net>
Cc: "linux-unionfs" <linux-unionfs@vger.kernel.org>,
	"fstests" <fstests@vger.kernel.org>,
	"amir73il" <amir73il@gmail.com>, "miklos" <miklos@szeredi.hu>,
	"guaneryu" <guaneryu@gmail.com>
Subject: 回复:system hang on a syncfs test with nfs_export enabled
Date: Thu, 30 Apr 2020 17:48:18 +0800	[thread overview]
Message-ID: <171ca7ca308.ed1c416b1605.5683082771269054301@mykernel.net> (raw)
In-Reply-To: <171ca5e76d2.11a198ab91526.7776557945472155733@mykernel.net>

 ---- 在 星期四, 2020-04-30 17:15:20 Chengguang Xu <cgxu519@mykernel.net> 撰写 ----
 > Hi 
 > 
 > I'm doing some tests for my new version of syncfs improvement patch and I found an 
 > interesting problem​ when combining dirty data && godown && nfs_export.
 > 
 > My expectation  is  Pass or Fail  all tests listed below, Test2 looks a bit strange and in my
 > opinion there is no strong connection between nfs_export/index and dirty data.
 > Any idea?
 > 
 > 
 > Test env and step like below:
 > 
 > Test1:
 > Compile module with nfs_export enabled
 > Run xfstest generic/474   ==> PASS
 > 
 > Test2:
 > Compile module with nfs_export enabled
 > Comment syncfs step in the test
 > Run xfstest generic/474   ==> Hang
 > 
 > Test3:
 > Compile module with nfs_export disabled
 > Run xfstest generic/474   ==> PASS
 > 
 > Test4:
 > Compile module with nfs_export disabled
 > Comment syncfs step in the test
 > Run xfstest generic/474   ==> FAIL
 > 

Additional information:

Overlayfs version: latest next branch of miklos tree (5.7-rc2)
Underlying fs: xfs

Thanks,
cgxu





  reply	other threads:[~2020-04-30  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  9:15 system hang on a syncfs test with nfs_export enabled Chengguang Xu
2020-04-30  9:48 ` Chengguang Xu [this message]
2020-04-30 12:22   ` Amir Goldstein
2020-05-02  4:10     ` Chengguang Xu
2020-05-02  9:17       ` Amir Goldstein

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=171ca7ca308.ed1c416b1605.5683082771269054301@mykernel.net \
    --to=cgxu519@mykernel.net \
    --cc=amir73il@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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