FS/XFS testing framework
 help / color / mirror / Atom feed
From: Chengguang Xu <cgxu519@mykernel.net>
To: "Amir Goldstein" <amir73il@gmail.com>
Cc: "linux-unionfs" <linux-unionfs@vger.kernel.org>,
	"fstests" <fstests@vger.kernel.org>, "miklos" <miklos@szeredi.hu>,
	"guaneryu" <guaneryu@gmail.com>
Subject: Re: system hang on a syncfs test with nfs_export enabled
Date: Sat, 02 May 2020 12:10:44 +0800	[thread overview]
Message-ID: <171d3944dec.fa74976d195.2610320131996757607@mykernel.net> (raw)
In-Reply-To: <CAOQ4uxgVRW9QKVg8edem2OKH1cjLF1+h5YW+nPfkoQg3OiaxgQ@mail.gmail.com>

 ---- 在 星期四, 2020-04-30 20:22:06 Amir Goldstein <amir73il@gmail.com> 撰写 ----
 > On Thu, Apr 30, 2020 at 12:48 PM Chengguang Xu <cgxu519@mykernel.net> wrote:
 > >
 > >  ---- 在 星期四, 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
 > >
 > 
 > Please test also against 5.7-rc2. Maybe we introduced some
 > regression in -next.
 > 
 > Please dump waiting processes stack by echo w > /proc/sysrq-trigger
 > to see where in kernel does the test hang.
 > 
 > I cannot think of anything in nfs_export/index that should affect
 > generic/474, but we will find out soon...
 > 

I‘m on vacation this week and it seems hard to reproduce the problem on my laptop, maybe there were some config problems.
I'll do more analyses next week on my testing machine.


Thanks,
cgxu




  reply	other threads:[~2020-05-02  4:11 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 ` 回复:system " Chengguang Xu
2020-04-30 12:22   ` system " Amir Goldstein
2020-05-02  4:10     ` Chengguang Xu [this message]
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=171d3944dec.fa74976d195.2610320131996757607@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