Cc overwriting file header

Thanks Lyndon for your quick reply about the number of MJ_CLOSEs. I
noticed though that the SectionObject pointer is never getting NULL, so
I think I have to implement the FCB tracking the hard way.

Now, can anyone explain this:
The cache manager is trying to overwrite the file’s header even though
the file has just been created. The header is for recognizing an
encrypted file and it is positioned at the end of file and ocuppies one
fully page. Actually, the worst thing is not that it is trying to
overwrite the header, but it is trying to set a new end of file to 4096,
one page length. What is determining the cache to act in that way and
what can I do to prevent this? What I forgot to say is, when a new end
of file is set the header is rewritten beyond that end of file, and in
this situation is wrong.

Daniel

You’re not interested in the SectionObjectPointer but the
DataSectionObject and the ImageSectionObject. Of course, you have to test if
the SectionObjectPointer is NULL before testing those fields, but the two
fields are important.

Daniel Turcanu wrote:

Thanks Lyndon for your quick reply about the number of MJ_CLOSEs. I
noticed though that the SectionObject pointer is never getting NULL, so
I think I have to implement the FCB tracking the hard way.

Now, can anyone explain this:
The cache manager is trying to overwrite the file’s header even though
the file has just been created. The header is for recognizing an
encrypted file and it is positioned at the end of file and ocuppies one
fully page. Actually, the worst thing is not that it is trying to
overwrite the header, but it is trying to set a new end of file to 4096,
one page length. What is determining the cache to act in that way and
what can I do to prevent this? What I forgot to say is, when a new end
of file is set the header is rewritten beyond that end of file, and in
this situation is wrong.

Daniel


You are currently subscribed to ntfsd as: xxxxx@alfasp.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


Kind regards, Dejan M. MVP for DDK
http://www.alfasp.com E-mail: xxxxx@alfasp.com
Alfa Transparent File Encryptor - Transparent file encryption services.
Alfa File Protector - File protection and hiding library for Win32
developers.
Alfa File Monitor - File monitoring library for Win32 developers.

if u are using a header at the end of the file, u will always have to
re-write it whenever the file size changes due to write or set eof.

Ampsi

----- Original Message -----
From: “Daniel Turcanu”
To: “File Systems Developers”
Sent: Friday, March 28, 2003 02:06
Subject: [ntfsd] Cc overwriting file header

Thanks Lyndon for your quick reply about the number of MJ_CLOSEs. I
noticed though that the SectionObject pointer is never getting NULL, so
I think I have to implement the FCB tracking the hard way.

Now, can anyone explain this:
The cache manager is trying to overwrite the file’s header even though
the file has just been created. The header is for recognizing an
encrypted file and it is positioned at the end of file and ocuppies one
fully page. Actually, the worst thing is not that it is trying to
overwrite the header, but it is trying to set a new end of file to 4096,
one page length. What is determining the cache to act in that way and
what can I do to prevent this? What I forgot to say is, when a new end
of file is set the header is rewritten beyond that end of file, and in
this situation is wrong.

Daniel


You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to xxxxx@lists.osr.com