| 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, 11 Dec 2006 18:30:49 +0100 From: Erik Mouw <erik@...ddisk-recovery.com> To: Maria Short <mgolod@...e.org> Cc: linux-kernel@...r.kernel.org Subject: Re: Linux slack space question On Fri, Dec 08, 2006 at 12:21:04PM -0500, Maria Short wrote: > I have a question regarding how the Linux kernel handles slack space. > I know that the ext3 filesystems typically use 1,2 or 4 KB blocks and > if a file is not an even multiple of the block size then the last > allocated block will not be completely filled, the remaining space is > wasted as slack space. > > What I need is the code in the kernel that does that. I have been > looking at http://lxr.linux.no/source/fs/ext3/inode.c but I could not > find the specific code for partially filling the last block and > placing an EOF at the end, leaving the rest to slack space. Think about it: what value would an EOF have if all byte values are allowed in a file? >From the very first Unix filesystem an inode contains both the number of blocks it contains and the actual file size. > Please forward the answer to mgolod@...e.org as soon as possible. Hmm no. You asked a public forum so the reply will go to that same public forum. See http://catb.org/esr/faqs/smart-questions.html#noprivate . Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - 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