| 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: Tue, 31 May 2011 20:39:42 -0400 From: Christoph Hellwig <hch@...radead.org> To: Hugh Dickins <hughd@...gle.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Christoph Hellwig <hch@...radead.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH 3/14] tmpfs: take control of its truncate_range > Note that drivers/gpu/drm/i915/i915_gem.c i915_gem_object_truncate() > calls the tmpfs ->truncate_range directly: update that in a separate > patch later, for now just let it duplicate the truncate_inode_pages(). > Because i915 handles unmap_mapping_range() itself at a different stage, > we have chosen not to bundle that into ->truncate_range. In your next series that makes it call the readpae replacement directly it might be nice to also call directly into shmem for hole punching. > I notice that ext4 is now joining ocfs2 and xfs in supporting fallocate > FALLOC_FL_PUNCH_HOLE: perhaps they should support truncate_range, and > tmpfs should support fallocate? But worry about that another time... No, truncate_range and the madvice interface are pretty sad hacks that should never have been added in the first place. Adding FALLOC_FL_PUNCH_HOLE support for shmem on the other hand might make some sense. -- 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