From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f72.google.com (mail-pl0-f72.google.com [209.85.160.72]) by kanga.kvack.org (Postfix) with ESMTP id 30D526B0003 for ; Sat, 14 Apr 2018 15:50:37 -0400 (EDT) Received: by mail-pl0-f72.google.com with SMTP id h12-v6so7885602pls.23 for ; Sat, 14 Apr 2018 12:50:37 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org. [2607:7c80:54:e::133]) by mx.google.com with ESMTPS id p23si7252932pfj.40.2018.04.14.12.50.35 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 14 Apr 2018 12:50:35 -0700 (PDT) Date: Sat, 14 Apr 2018 12:50:30 -0700 From: Matthew Wilcox Subject: Re: [PATCH v10 00/62] Convert page cache to XArray Message-ID: <20180414195030.GB31523@bombadil.infradead.org> References: <20180330034245.10462-1-willy@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Goldwyn Rodrigues Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, Matthew Wilcox , Jan Kara , Jeff Layton , Lukas Czerner , Ross Zwisler , Christoph Hellwig , Nicholas Piggin , Ryusuke Konishi , linux-nilfs@vger.kernel.org, Jaegeuk Kim , Chao Yu , linux-f2fs-devel@lists.sourceforge.net, Oleg Drokin , Andreas Dilger , James Simmons , Mike Kravetz On Mon, Apr 09, 2018 at 04:18:07PM -0500, Goldwyn Rodrigues wrote: I'm sorry I missed this email. My inbox is a disaster :( > I tried these patches against next-20180329 and added the patch for the > bug reported by Mike Kravetz. I am getting the following BUG on ext4 and > xfs, running generic/048 tests of fstests. Each trace is from a > different instance/run. Yikes. I haven't been able to reproduce this. Maybe it's a matter of filesystem or some other quirk. It seems easy for you to reproduce it, so would you mind bisecting it? Should be fairly straightforward; I'd start at commit "xarray: Add MAINTAINERS entry", since the page cache shouldn't be affected by anything up to that point, then bisect forwards from there. > BTW, for my convenience, do you have these patches in a public git tree? I didn't publish it; it's hard to push out a tree based on linux-next. I'll try to make that happen.