All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 201259] New: [xfstests shared/010]: maybe pagecache contents is mutated after cycle mount
Date: Fri, 28 Sep 2018 06:06:53 +0000	[thread overview]
Message-ID: <bug-201259-201763@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=201259

            Bug ID: 201259
           Summary: [xfstests shared/010]: maybe pagecache contents is
                    mutated after cycle mount
           Product: File System
           Version: 2.5
    Kernel Version: v4.19-rc5
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: zlang@redhat.com
        Regression: No

Recently, shared/010 sometimes hit below issue:

QA output created by 010
/mnt/scratch/dir/p0/deXXXXXXXXXXX/d218X/d3a0XXX/d3da/d90XXXXXXXXXXXXX/d1c8XXXXXXXXX/d71/d75XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/da6XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/db9XXXX/de0XXXXXXXXXXXXX/d7e0XXXXXXXXXXXX/d1d9X/f476XXXX:
FAILED
md5sum: WARNING: 1 computed checksum did NOT match
Silence is golden

Looks like something changed after cycle mount, cause this integrity issue.

Version-Release number of selected component (if applicable):
kernel v4.19-rc5

How reproducible:
10~30%

Steps to Reproduce:
1) git clone https://github.com/markfasheh/duperemove.git
2) cd duperemove; make; make install
3) Run shared/010 on XFS several times, with reflink=1:

Actual results:
checksum mismatch

Expected results:
test always pass

Additional info:
I can't be sure this's a real bug, maybe it's case issue. But I don't know
what's wrong with the case, so report this bug to get more
reviewing/suggestions from XFS developers. Thanks.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2018-09-28 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28  6:06 bugzilla-daemon [this message]
2018-10-02 13:53 ` [Bug 201259] [xfstests shared/010]: maybe pagecache contents is mutated after cycle mount bugzilla-daemon
2018-10-02 13:54 ` bugzilla-daemon
2018-10-02 16:24 ` bugzilla-daemon
2018-10-02 16:28 ` bugzilla-daemon
2018-10-02 16:37 ` bugzilla-daemon
2018-11-03  3:05 ` bugzilla-daemon
2018-11-03  3:11 ` bugzilla-daemon
2018-11-05 22:44 ` bugzilla-daemon
2018-11-06  3:14 ` bugzilla-daemon

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=bug-201259-201763@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.