| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 28 Jul 2014 08:32:19 -0400 From: Sasha Levin <sasha.levin@...cle.com> To: Andrey Ryabinin <a.ryabinin@...sung.com>, "Kirill A. Shutemov" <kirill@...temov.name> CC: Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Andi Kleen <ak@...ux.intel.com>, Matthew Wilcox <matthew.r.wilcox@...el.com>, Dave Hansen <dave.hansen@...ux.intel.com>, Alexander Viro <viro@...iv.linux.org.uk>, Dave Chinner <david@...morbit.com>, Ning Qu <quning@...il.com>, linux-mm@...ck.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, Dave Jones <davej@...hat.com>, stable@...r.kernel.org, "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>, Mel Gorman <mgorman@...e.de>, Rik van Riel <riel@...hat.com>, Konstantin Khlebnikov <koct9i@...il.com>, Hugh Dickins <hughd@...gle.com> Subject: Re: [PATCH] mm: don't allow fault_around_bytes to be 0 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists