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
| ||
|
Message-ID: <53C7F55B.8030307@suse.cz> Date: Thu, 17 Jul 2014 18:10:03 +0200 From: Vlastimil Babka <vbabka@...e.cz> To: Hugh Dickins <hughd@...gle.com>, Andrew Morton <akpm@...ux-foundation.org> CC: Sasha Levin <sasha.levin@...cle.com>, Konstantin Khlebnikov <koct9i@...il.com>, Johannes Weiner <hannes@...xchg.org>, Michel Lespinasse <walken@...gle.com>, Lukas Czerner <lczerner@...hat.com>, Dave Jones <davej@...hat.com>, linux-mm@...ck.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/2] shmem: fix faulting into a hole while it's punched, take 3 On 07/15/2014 12:28 PM, Hugh Dickins wrote: > In the end I decided that we had better look at it as two problems, > the trinity faulting starvation, and the indefinite punching loop, > so 1/2 and 2/2 present both solutions: belt and braces. I tested that with my reproducer and it was OK, but as I already said, it's not trinity so I didn't observe the new problems in the first place. > Which may be the best for fixing, but the worst for ease of backporting. > Vlastimil, I have prepared (and lightly tested) a 3.2.61-based version > of the combination of f00cdc6df7d7 and 1/2 and 2/2 (basically, I moved > vmtruncate_range from mm/truncate.c to mm/shmem.c, since nothing but > shmem ever implemented the truncate_range method). It should give a I don't know how much stable kernel updates are supposed to care about out-of-tree modules, but doesn't the change mean that an out-of-tree FS supporting truncate_range (if such thing exists) would effectively stop supporting madvise(MADV_REMOVE) after this change? But hey it's still madvise so maybe we don't need to care. And I suppose kernels where FALLOC_FL_PUNCH_HOLE is supported, can be backported normally. > good hint for backports earlier and later: I'll send it privately to > you now, but keep in mind that it may need to be revised if today's > patches for 3.16 get revised again (I'll send it to Ben Hutchings > only when that's settled). > > Thanks, > Hugh > -- 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