From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ipmail07.adl2.internode.on.net ([150.101.137.131]:52632 "EHLO ipmail07.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751617AbcLLCwv (ORCPT ); Sun, 11 Dec 2016 21:52:51 -0500 Date: Mon, 12 Dec 2016 13:52:21 +1100 From: Dave Chinner To: Ross Zwisler , xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org Subject: Re: XFS: Assertion failed: del->br_blockcount > 0, file: fs/xfs/libxfs/xfs_bmap.c, line: 5124 Message-ID: <20161212025221.GV4326@dastard> References: <20161209224214.GA2254@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161209224214.GA2254@linux.intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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@fromorbit.com