determining if io will hit status_file_lock_conflict

NTFSD
1

hi,

is there a way for filter drivers to determine before sending down a read or
write irp that the irp will be returned with a status_file_lock_conflict?

thanks!

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein

2

You could track the lock state in your filter. This is of course error prone since it is a duplication of code.

-----Original Message-----
From: Ho Mun Chuen [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Tuesday, October 29, 2002 3:40 AM
To: File Systems Developers
Subject: [ntfsd] determining if io will hit status_file_lock_conflict

hi,

is there a way for filter drivers to determine before sending down a read or
write irp that the irp will be returned with a status_file_lock_conflict?

thanks!

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein

You are currently subscribed to ntfsd as: xxxxx@inin.com
To unsubscribe send a blank email to %%email.unsub%%

3

and it would fail if used on a rdr filter, because it will never know what
has been locked by other rdrs.

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein
----- Original Message -----
From: “Fuller, Rob”
To: “File Systems Developers”
Sent: Tuesday, October 29, 2002 9:56 PM
Subject: [ntfsd] RE: determining if io will hit status_file_lock_conflict

You could track the lock state in your filter. This is of course error
prone since it is a duplication of code.

-----Original Message-----
From: Ho Mun Chuen [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Tuesday, October 29, 2002 3:40 AM
To: File Systems Developers
Subject: [ntfsd] determining if io will hit status_file_lock_conflict

hi,

is there a way for filter drivers to determine before sending down a read or
write irp that the irp will be returned with a status_file_lock_conflict?

thanks!

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein

—
You are currently subscribed to ntfsd as: xxxxx@inin.com
To unsubscribe send a blank email to %%email.unsub%%

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to %%email.unsub%%

4

Is there some reason you can’t filter the file system on the server side?

-----Original Message-----
From: Ho Mun Chuen [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Tuesday, October 29, 2002 8:17 PM
To: File Systems Developers
Subject: [ntfsd] RE: determining if io will hit
status_file_lock_conflict

and it would fail if used on a rdr filter, because it will never know what
has been locked by other rdrs.

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein
----- Original Message -----
From: “Fuller, Rob”
To: “File Systems Developers”
Sent: Tuesday, October 29, 2002 9:56 PM
Subject: [ntfsd] RE: determining if io will hit status_file_lock_conflict

You could track the lock state in your filter. This is of course error
prone since it is a duplication of code.

-----Original Message-----
From: Ho Mun Chuen [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Tuesday, October 29, 2002 3:40 AM
To: File Systems Developers
Subject: [ntfsd] determining if io will hit status_file_lock_conflict

hi,

is there a way for filter drivers to determine before sending down a read or
write irp that the irp will be returned with a status_file_lock_conflict?

thanks!

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein

—
You are currently subscribed to ntfsd as: xxxxx@inin.com
To unsubscribe send a blank email to %%email.unsub%%

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to %%email.unsub%%

—
You are currently subscribed to ntfsd as: xxxxx@inin.com
To unsubscribe send a blank email to %%email.unsub%%

5

i am writing the filter for clients and not the server. moreover, it would
be quite complicated for the filter on the clients to ask the filter on the
server for the byte lock info, rite?

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein
----- Original Message -----
From: “Fuller, Rob”
To: “File Systems Developers”
Sent: Wednesday, October 30, 2002 10:18 PM
Subject: [ntfsd] RE: determining if io will hit status_file_lock_conflict

Is there some reason you can’t filter the file system on the server side?

-----Original Message-----
From: Ho Mun Chuen [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Tuesday, October 29, 2002 8:17 PM
To: File Systems Developers
Subject: [ntfsd] RE: determining if io will hit
status_file_lock_conflict

and it would fail if used on a rdr filter, because it will never know what
has been locked by other rdrs.

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein
----- Original Message -----
From: “Fuller, Rob”
To: “File Systems Developers”
Sent: Tuesday, October 29, 2002 9:56 PM
Subject: [ntfsd] RE: determining if io will hit status_file_lock_conflict

You could track the lock state in your filter. This is of course error
prone since it is a duplication of code.

-----Original Message-----
From: Ho Mun Chuen [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Tuesday, October 29, 2002 3:40 AM
To: File Systems Developers
Subject: [ntfsd] determining if io will hit status_file_lock_conflict

hi,

is there a way for filter drivers to determine before sending down a read or
write irp that the irp will be returned with a status_file_lock_conflict?

thanks!

Ho Mun Chuen
@@ “Not everything that counts can be counted;
<” )~ and not everything that can be counted counts"
//\ … Albert Einstein

—
You are currently subscribed to ntfsd as: xxxxx@inin.com
To unsubscribe send a blank email to %%email.unsub%%

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to %%email.unsub%%

—
You are currently subscribed to ntfsd as: xxxxx@inin.com
To unsubscribe send a blank email to %%email.unsub%%

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to %%email.unsub%%