linux-kernel - Re: Linux slack space question

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0612081337510.20280@chaos.analogic.com>
Date:	Fri, 8 Dec 2006 13:51:44 -0500
From:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To:	"Maria Short" <mgolod@...e.org>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: Linux slack space question

On Fri, 8 Dec 2006, 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.
>

Not wasted, could be extended if additional data are written.

> 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.

An EOF? Unlike CP/M the Linux file-systems copy to user-space up to the
last byte written to the file, not up to the last block. Therefore, there
is no need for "fill" and certainly no EOF character. All Linux/Unix
files are binary files, i.e., there are no special characters inserted.
Now, when you read a file using buffered I/O (the f***() functions), the
'C' runtime library converts I/O so that functions like feof(*stream) work.
The actual EOF on a binary file occurs when a read() returns 0 bytes.

The number of bytes actually written to files are handled in inodes. In fact, 
you can make a file larger simply by moving a file-pointer. That changes
the inode value. Such files are called sparse files and, when read, the space 
not written is cleared so the user never reads something that wasn't
specifically written.

  >
> Please forward the answer to mgolod@...e.org as soon as possible.
>
> Thank you very much.
> -

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.68 BogoMips).
New book: http://www.AbominableFirebug.com/
_
..

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
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/