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, 15 Sep 2008 10:53:05 -0700 From: Mark Fasheh <mfasheh@...e.com> To: Christoph Hellwig <hch@...radead.org> Cc: Theodore Tso <tytso@....EDU>, Anton Altaparmakov <aia21@....ac.uk>, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, akpm@...uxfoundation.org Subject: Re: [PATCH 1/4] vfs: vfs-level fiemap interface On Mon, Sep 15, 2008 at 10:49:48AM -0400, Christoph Hellwig wrote: > I agree to you (or someone elses - don't remember anymore) suggestion > to put in more padding so we can add fields later. I strongly disagree > putting in features now that we neither have a user, nor a usecase or > testcase for. So, how about another 64 bits of padding in struct fiemap_extent? That could help cover future uses like compression, which might require another 64 bit offset field - we only have 32 bits of reserved space there right now. --Mark -- Mark Fasheh -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists