linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Charlie Gordon" <gmane@chqrlie.org>
To: linux-c-programming@vger.kernel.org
Subject: Re: How to allocate few bytes to a file automatically after creating it?
Date: Thu, 13 May 2004 09:53:27 +0200	[thread overview]
Message-ID: <c7v9ep$fcp$1@sea.gmane.org> (raw)
In-Reply-To: 20040513015353.37BCC1E453@xprdmailfe25.nwk.excite.com

> My aim is to allocate few bytes to a file; with some valid data in it as
soon as it is created. Will the following approach work?
>
> Calling the function ext2_direct_IO() with the appropriate parameters
after creating a new inode. The appro. parameters are rw flag, inode, iobuf,
blocknr, blocksize.
> If I want to add just 100 bytes to the file, I guess blocknr should be 1
and blocksize should be 512 or 1024 .. is that right? Also, how to fill in
"iobuf" which is of the type "struct kiobuf *" to add these 100 bytes?
>

Are you doing this from a driver ?
Fiddling with file system specific stuff seems overkill for your purpose.
If your goal is to make sure the file is non empty, with correct contents,
as soon as it appears in the file system, the classical method is to create
a new file with a temporary name with open(), write appropriate contents to
it with write(), close it, and then rename it to the correct name with
rename(), an atomic change to most file systems.  The only constraint is
that the file be created in the same file system.

If this doesn't solve your problem, what did I miss ?

Chqrlie.




      reply	other threads:[~2004-05-13  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13  1:53 How to allocate few bytes to a file automatically after creating it? Vineet Joglekar
2004-05-13  7:53 ` Charlie Gordon [this message]

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='c7v9ep$fcp$1@sea.gmane.org' \
    --to=gmane@chqrlie.org \
    --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).