From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <53D642D3.8020407@oracle.com> Date: Mon, 28 Jul 2014 08:32:19 -0400 From: Sasha Levin MIME-Version: 1.0 To: Andrey Ryabinin , "Kirill A. Shutemov" CC: Andrew Morton , Linus Torvalds , Andi Kleen , Matthew Wilcox , Dave Hansen , Alexander Viro , Dave Chinner , Ning Qu , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Dave Jones , stable@vger.kernel.org, "Kirill A. Shutemov" , Mel Gorman , Rik van Riel , Konstantin Khlebnikov , Hugh Dickins Subject: Re: [PATCH] mm: don't allow fault_around_bytes to be 0 References: <53D07E96.5000006@oracle.com> <1406533400-6361-1-git-send-email-a.ryabinin@samsung.com> <20140728093611.GA3975@node.dhcp.inet.fi> <53D62599.6000605@samsung.com> In-Reply-To: <53D62599.6000605@samsung.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 07/28/2014 06:27 AM, Andrey Ryabinin wrote: >> Although, I'm not convinced that it caused the issue. Sasha, did you touch the >> > debugfs handle? >> > > I suppose trinity could change it, no? I've got the very same spew after setting fault_around_bytes to 0. Not on purpose, but as Andrey said - it's very possible that trinity did. Thanks, Sasha