linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vineet Joglekar" <vintya@excite.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: Can I allocate few bytes in a file to store info about that file; not visible to user?
Date: Wed, 28 Apr 2004 14:15:07 -0400 (EDT)	[thread overview]
Message-ID: <20040428181507.B489EB786@xprdmailfe20.nwk.excite.com> (raw)



>Well, you can achieve almost anything if you're willing to spend >enough effort modifying the kernel. But what you are proposing >would be a lot of work; probably much more than you're expecting.
>--Glynn Clements <glynn.clements@virgin.net>

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

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!

             reply	other threads:[~2004-04-28 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 18:15 Vineet Joglekar [this message]
2004-04-29  3:58 ` Can I allocate few bytes in a file to store info about that file; not visible to user? Vadiraj C S
  -- strict thread matches above, loose matches on Subject: below --
2004-04-26 14:32 Vineet Joglekar
2004-04-26 17:05 ` Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040428181507.B489EB786@xprdmailfe20.nwk.excite.com \
    --to=vintya@excite.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).