From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:46902 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727603AbfGSV3F (ORCPT ); Fri, 19 Jul 2019 17:29:05 -0400 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 1A9412892A for ; Fri, 19 Jul 2019 21:29:05 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 204049] [xfstests generic/388]: XFS: Assertion failed: ip->i_d.di_format != XFS_DINODE_FMT_BTREE || ip->i_d.di_nextents > XFS_IFORK_MAXEXT(ip, XFS_DATA_FORK), file: fs/xfs/xfs_inode.c, line: 3646 Date: Fri, 19 Jul 2019 21:29:04 +0000 Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: linux-xfs@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=204049 --- Comment #5 from Luis Chamberlain (mcgrof@kernel.org) --- (In reply to Luis Chamberlain from comment #4) > The crash observed on stable kernels can be fixed with commit 6958d11f77 > ("xfs: don't trip over uninitialized buffer on extent read of corrupted > inode") merged on v5.1. > > I can't reproduce the immediate panic on v5.1 with the > "xfs_reflink_normapbt" anymore, as such I believe this seems like a > regression, and you should be able to bisect to v5.1 as the good kernel. Correction, it just took longer to crash. Same crash as in kz#204223 [0] on v5.1. That issue is still not fixed. [0] https://bugzilla.kernel.org/show_bug.cgi?id=204223 -- You are receiving this mail because: You are watching the assignee of the bug.