Filter manager access to FILE_LOCK

NTFSD
1

Is there any mechanism in the filter manager to manipulate FILE_LOCKs? My
legacy driver that I am porting uses the FsRtl lock routines
(FsRtlCheckLockForReadAccess, etc). But these all take an Irp parameter and
so are not usable in a filter driver.

Do I have to implement my own byte range locking implementation, acting on
the FLT_CALLBACK_DATA? I realise it can be done fairly mechanically, and
will be self-contained. But it is general purpose library code I would
prefer not to have to write myself.

Brian

2

Brian,

This was an oversight. We will add the appropriate routines to handle
this.

Thank you,

Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian Collins
Sent: Monday, April 26, 2004 8:29 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Filter manager access to FILE_LOCK

Is there any mechanism in the filter manager to manipulate FILE_LOCKs?
My
legacy driver that I am porting uses the FsRtl lock routines
(FsRtlCheckLockForReadAccess, etc). But these all take an Irp parameter
and
so are not usable in a filter driver.

Do I have to implement my own byte range locking implementation, acting
on
the FLT_CALLBACK_DATA? I realise it can be done fairly mechanically, and
will be self-contained. But it is general purpose library code I would
prefer not to have to write myself.

Brian

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

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

3

Thanks Neal

Brian

“Neal Christiansen” wrote in message
news:xxxxx@ntfsd…
Brian,

This was an oversight. We will add the appropriate routines to handle
this.

Thank you,

Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian Collins
Sent: Monday, April 26, 2004 8:29 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Filter manager access to FILE_LOCK

Is there any mechanism in the filter manager to manipulate FILE_LOCKs?
My
legacy driver that I am porting uses the FsRtl lock routines
(FsRtlCheckLockForReadAccess, etc). But these all take an Irp parameter
and
so are not usable in a filter driver.

Do I have to implement my own byte range locking implementation, acting
on
the FLT_CALLBACK_DATA? I realise it can be done fairly mechanically, and
will be self-contained. But it is general purpose library code I would
prefer not to have to write myself.

Brian

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

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

4

Neal -

You wouldn’t be thinking of adding support for all the FsRtl “locking”
functions would you :wink:
Wouldn’t calls like FsRtlIntilizeFileLock & FsRtlProcessFileLock add new
completion/callback semantics?

Just wondering…

/ted

-----Original Message-----
From: Neal Christiansen [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, April 27, 2004 2:08 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Filter manager access to FILE_LOCK

Brian,

This was an oversight. We will add the appropriate routines to handle this.

Thank you,

Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian Collins
Sent: Monday, April 26, 2004 8:29 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Filter manager access to FILE_LOCK

Is there any mechanism in the filter manager to manipulate FILE_LOCKs? My
legacy driver that I am porting uses the FsRtl lock routines
(FsRtlCheckLockForReadAccess, etc). But these all take an Irp parameter and
so are not usable in a filter driver.

Do I have to implement my own byte range locking implementation, acting on
the FLT_CALLBACK_DATA? I realise it can be done fairly mechanically, and
will be self-contained. But it is general purpose library code I would
prefer not to have to write myself.

Brian

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

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

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

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