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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c698a820612080921u20a957d9x1ac1e01e6734d025@mail.gmail.com>
Date:	Fri, 8 Dec 2006 12:21:04 -0500
From:	"Maria Short" <mgolod@...e.org>
To:	linux-kernel@...r.kernel.org
Subject: Linux slack space question

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.

Please forward the answer to mgolod@...e.org as soon as possible.

Thank you very much.
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ