From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 200137] [xfstests generic/485] XFS: Assertion failed: (irec->br_startoff & ~XFS_IEXT_STARTOFF_MASK) == 0, file: fs/xfs/libxfs/xfs_iext_tree.c, line: 68
Date: Tue, 19 Jun 2018 18:46:40 +0000 [thread overview]
Message-ID: <bug-200137-201763-y9BdpFPj5J@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200137-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200137
--- Comment #2 from Zorro Lang (zlang@redhat.com) ---
(In reply to Darrick J. Wong from comment #1)
> Created attachment 276691 [details]
> proposed fix
>
> Zoro: does the attached patch fix the problem?
Hi Darrick,
Yes, I can't reproduce this bug again after merged your patch:
# mkfs.xfs -f -m crc=0 -b size=512 /dev/mapper/xxxx-xfstest
meta-data=/dev/mapper/xxxx-xfstest isize=256 agcount=4, agsize=10485760 blks
= sectsz=512 attr=2, projid32bit=1
= crc=0 finobt=0, sparse=0, rmapbt=0
= reflink=0
data = bsize=512 blocks=41943040, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=512 blocks=20480, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
# ./check generic/485
FSTYP -- xfs (debug)
PLATFORM -- Linux/x86_64 xxx.xxx.xxx 4.17.0+
MKFS_OPTIONS -- -f -m crc=0 -b size=512 /dev/mapper/xxxx-xfscratch
MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0
/dev/mapper/xxxx-xfscratch /mnt/scratch
generic/485 2s
Ran: generic/485
Passed all 1 tests
Thanks,
Zorro
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-06-19 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 9:30 [Bug 200137] New: [xfstests generic/485] XFS: Assertion failed: (irec->br_startoff & ~XFS_IEXT_STARTOFF_MASK) == 0, file: fs/xfs/libxfs/xfs_iext_tree.c, line: 68 bugzilla-daemon
2018-06-19 17:10 ` [Bug 200137] " bugzilla-daemon
2018-06-19 18:46 ` bugzilla-daemon [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=bug-200137-201763-y9BdpFPj5J@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.