Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, fstests <fstests@vger.kernel.org>
Subject: Re: generic/127 failure on xfs with hacked fsx
Date: Wed, 14 Mar 2018 14:18:51 -0700	[thread overview]
Message-ID: <20180314211851.GW4865@magnolia> (raw)
In-Reply-To: <CAJfpegs=RenwFojwAze_y7WF3hwiNu-+5qDw_wyT=o0M063HkQ@mail.gmail.com>

On Wed, Mar 14, 2018 at 04:50:02PM +0100, Miklos Szeredi wrote:
> While testing overlayfs I found something which appears to be an
> unwanted side effect of xfs_release().
> 
> Apply the attached patch to xfstests and run generic/127.
> 
> Result is:
> 
>     +ltp/fsx -q -l 262144 -o 65536 -S 191110531 -N 100000 fsx_std_mmap
>     +Mapped Read: non-zero data past EOF (0x8aa1) page offset 0xaa2 is 0xa091
>     +LOG DUMP (70315 total operations):
> 
> Thanks,
> Miklos

Hmm.... so I applied this and ran generic/127 on xfs:

FSTYP         -- xfs (debug)
PLATFORM      -- Linux/x86_64 magnolia-mtr00 4.16.0-rc5-xfsx
MKFS_OPTIONS  -- -f -m reflink=1,rmapbt=1, -i sparse=1, /dev/pmem4
MOUNT_OPTIONS -- -o usrquota,grpquota,prjquota, /dev/sda /opt

generic/127      53s
Ran: generic/127
Passed all 1 tests

Reran a couple of times without seeing any problems, so what am
I missing?  Are you running xfstests atop overlayfs atop xfs?

/me confused. :/

--D

> ---
>  ltp/fsx.c |    9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> --- a/ltp/fsx.c
> +++ b/ltp/fsx.c
> @@ -647,6 +647,14 @@ check_trunc_hack(void)
>  	}
>  }
>  
> +static void openclose(int fd)
> +{
> +	char path[32];
> +
> +	sprintf(path, "/proc/self/fd/%i", fd);
> +	close(open(path, O_RDONLY));
> +}
> +
>  void
>  doflush(unsigned offset, unsigned size)
>  {
> @@ -799,6 +807,7 @@ domapread(unsigned offset, unsigned size
>  	        prterr("domapread: mmap");
>  		report_failure(190);
>  	}
> +	openclose(fd);
>  	memcpy(temp_buf, p + pg_offset, size);
>  
>  	check_eofpage("Read", offset, p, size);


  reply	other threads:[~2018-03-14 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 15:50 generic/127 failure on xfs with hacked fsx Miklos Szeredi
2018-03-14 21:18 ` Darrick J. Wong [this message]
2018-03-14 21:27   ` Dave Chinner
2018-03-15  7:58     ` Miklos Szeredi

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=20180314211851.GW4865@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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