| To: | Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS: Assertion failed: del->br_blockcount > 0, file: fs/xfs/libxfs/xfs_bmap.c, line: 5124 |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Mon, 12 Dec 2016 13:52:21 +1100 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20161209224214.GA2254@xxxxxxxxxxxxxxx> |
| References: | <20161209224214.GA2254@xxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Fri, Dec 09, 2016 at 03:42:14PM -0700, Ross Zwisler wrote:
> I'm able to consistently hit the following XFS assertion with v4.9-rc8 and
> xfstest xfs/118 (log is passed through kasan_symbolize.py):
commit 4dfce57db635 ("xfs: fix up xfs_swap_extent_forks inline
extent handling") in the XFS for-next tree.
Ross - when you get a failure in a brand new test in xfstests
(xfs/118 was merged about a month ago), it's worth checking whether
the problem is already fixed in the XFS for-next tree. In general,
the regression tests exercising such bugs aren't merged until the
fix has been committed...
> Kernel v4.8 is also able to his this same issue.
Yes. The above commit is marked for stable, so it will be appearing
in all those older kernels in the next few weeks...
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | XFS: Assertion failed: del->br_blockcount > 0, file: fs/xfs/libxfs/xfs_bmap.c, line: 5124, Ross Zwisler |
|---|---|
| Next by Date: | FOB Prices Request, FOB |
| Previous by Thread: | XFS: Assertion failed: del->br_blockcount > 0, file: fs/xfs/libxfs/xfs_bmap.c, line: 5124, Ross Zwisler |
| Next by Thread: | Re: XFS: Assertion failed: del->br_blockcount > 0, file: fs/xfs/libxfs/xfs_bmap.c, line: 5124, Ross Zwisler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |