headers
Vineet Joglekar | 14 Apr 2004 20:31
Picon
Favicon

Can I increase size of Inodes?


Hi all,

Is it possible to increase size of ext2_inode struct ? If yes, does it have to be in multiples of something?
(say 128 bytes?) What all things do I need to take care of / change; if I am changing the size of the inode? I
suppose inode bitmap will be one of them...

Thanks and regards,

Vineet

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
-
To unsubscribe from this list: send the line "unsubscribe linux-fsf" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Vineet Joglekar | 26 Apr 2004 16:31
Picon
Favicon

Can I allocate few bytes in a file to store info about that file; not visible to user?


Hi all,

In ext2fs, while creating a file, can I allocate a number of bytes for that file in advance, such that those
bytes are not seen by the user? that is,

suppose I am creating a new file temp, then allocate 50 bytes immediately after creating the file. I want to
use those bytes to store the file related info; accessible only to kernel. Whatever data user wants to add,
will be added after the these 50 bytes. If user does lseek(fd,0,SEEK_SET), then the file pointer should
point to the 51st byte. The 1st 50 bytes shouldnt be visible to user. I dont care if the file size is shown as
userdata+50. Is it possible to achieve? If yes, how?

Thanks and regards,

Vineet

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
-
To unsubscribe from this list: send the line "unsubscribe linux-fsf" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Vineet Joglekar | 28 Apr 2004 20:16
Picon
Favicon

RE: Can I allocate few bytes in a file to store info about that file; not visible to user?


Hi all,

I was going through the functions like generic_file_write, generic_file_direct_IO,
generic_direct_IO and filemap_fdatasync. I was thinking about calling these functions or calling
functions written on similar lines to add new few bytes to the file when the inode is created by
"ext2_create()". Can any1 please tell me how to do this?

I guess it would have been simpler to call these functions in the call sys_open() when a new file is created,
but I want to make changes in kernel code only in ext2 module. playing with sys_open will be like modifying
kernel code apart from the ext2 fs module which I dont want.

Thanks and regards,

Vineet

 --- On Mon 04/26, Vineet Joglekar < vintya <at> excite.com > wrote:
From: Vineet Joglekar [mailto: vintya <at> excite.com]
To: linux-fsf <at> vger.kernel.org
Date: Mon, 26 Apr 2004 10:31:19 -0400
Subject: Can I allocate few bytes in a file to store info about that file; not visible to user?

Hi all,<br><br>In ext2fs, while creating a file, can I allocate a number of bytes for that file in advance,
such that those bytes are not seen by the user? that is,<br><br>suppose I am creating a new file temp, then
allocate 50 bytes immediately after creating the file. I want to use those bytes to store the file related
info; accessible only to kernel. Whatever data user wants to add, will be added after the these 50 bytes. If
user does lseek(fd,0,SEEK_SET), then the file pointer should point to the 51st byte. The 1st 50 bytes
shouldnt be visible to user. I dont care if the file size is shown as userdata+50. Is it possible to achieve?
If yes, how?<br><br>Thanks and
regards,<br><br>Vineet<br><br>_______________________________________________<br>Join
(Continue reading)

Permalink | Reply | 0 comments |

Gmane