byte lock behaviour

NTFSD
1

hi,

to my knowledge, byte locks are process specific. so different threads
belonging to the same process should be able to pass the locks if their key
values are the same.

but i have encountered a situation where a file exclusively locked at 4576
length 1 key 0 file object 810c0330 processid ffb85da8 and at 4577 length 1
key 0 file object 811005e8 processid ffb85da8, gets a file lock conflict
error when process ffb85da8 tries to write from 4608 length 8192 bytes using
file object 810c0330.

i thought byte locks are dealing with the file stream… but what i
encountered seems to say it is file object specific?

Ampsi

2

so sorry, just got my “File Systems Internals” back from a colleague and
read that to unlock a byte range, the file object must also match.

so i guess byte lock checks for read/write request will take the file object
into consideration.

Ampsi

----- Original Message -----
From: “Ampsi Ho”
To: “Windows File Systems Devs Interest List”
Sent: Wednesday, October 08, 2003 19:41
Subject: [ntfsd] byte lock behaviour

hi,

to my knowledge, byte locks are process specific. so different threads
belonging to the same process should be able to pass the locks if their key
values are the same.

but i have encountered a situation where a file exclusively locked at 4576
length 1 key 0 file object 810c0330 processid ffb85da8 and at 4577 length 1
key 0 file object 811005e8 processid ffb85da8, gets a file lock conflict
error when process ffb85da8 tries to write from 4608 length 8192 bytes using
file object 810c0330.

i thought byte locks are dealing with the file stream… but what i
encountered seems to say it is file object specific?

Ampsi

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