Re: [PATCH] mm: don't allow fault_around_bytes to be 0 | stable | Ratatoskr

(off-list ancestor, not in this archive)
[PATCH] mm: don't allow fault_around_bytes to be 0 · Andrey Ryabinin <hidden> · 2014-07-28
Re: [PATCH] mm: don't allow fault_around_bytes to be 0 · Andrey Ryabinin <hidden> · 2014-07-28
Re: [PATCH] mm: don't allow fault_around_bytes to be 0 · Kirill A. Shutemov <hidden> · 2014-07-28
Re: [PATCH] mm: don't allow fault_around_bytes to be 0 · Andrey Ryabinin <hidden> · 2014-07-28
Re: [PATCH] mm: don't allow fault_around_bytes to be 0 · Kirill A. Shutemov <hidden> · 2014-07-28
Re: [PATCH] mm: don't allow fault_around_bytes to be 0 · Sasha Levin <hidden> · 2014-07-28
Re: [PATCH] mm: don't allow fault_around_bytes to be 0 · David Rientjes <rientjes@google.com> · 2014-07-28
Re: [PATCH] mm: don't allow fault_around_bytes to be 0 · Dave Hansen <dave.hansen@linux.intel.com> · 2014-07-28

Re: [PATCH] mm: don't allow fault_around_bytes to be 0

From: Sasha Levin <hidden>
Date: 2014-07-28 12:32:19
Also in: linux-fsdevel, linux-mm, lkml

On 07/28/2014 06:27 AM, Andrey Ryabinin wrote:

quoted

Although, I'm not convinced that it caused the issue. Sasha, did you touch the

quoted

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