| 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: Sat, 30 Jun 2007 12:13:40 +0100 From: Christoph Hellwig <hch@...radead.org> To: Jeff Garzik <jeff@...zik.org> Cc: Christoph Hellwig <hch@...radead.org>, Nick Piggin <npiggin@...e.de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Memory Management List <linux-mm@...ck.org>, linux-fsdevel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [RFC] fsblock On Sat, Jun 30, 2007 at 07:10:27AM -0400, Jeff Garzik wrote: > >Not really, the current behaviour is a bug. And it's not actually buffer > >layer specific - XFS now has a fix for that bug and it's generic enough > >that everyone could use it. > > I'm not sure I follow. If you require block allocation at mmap(2) time, > rather than when a page is actually dirtied, you are denying userspace > the ability to do sparse files with mmap. > > A quick Google readily turns up people who have built upon the > mmap-sparse-file assumption, and I don't think we want to break those > assumptions as a "bug fix." > > Where is the bug? It's not mmap time but page dirtying time. Currently the default behaviour is not to allocate at page dirtying time but rather at writeout time in some scenarious. (and s/allocation/reservation/ applies for delalloc of course) - 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