STATUS_FILE_LOCK_CONFLICT vs STATUS_LOCK_NOT_GRANTED?

NTFSD
1

Does anyone know the difference between STATUS_LOCK_NOT_GRANTED and
STATUS_FILE_LOCK_CONFLICT?

Thanks.

Neil

2

STATUS_LOCK_NOT_GRANTED means an attempt to acquire a lock failed

STATUS_FILE_LOCK_CONFLICT means an attempt to do an operation failed
because of existing locks that prevented it (reads/writes, by non-owning
processes, etc.)

Note that S_F_L_C is heavily reused as a way of backing out of
operations to retry them, along with STATUS_VERIFY_REQUIRED. I don’t
know why you are asking this question, but if you’re seeing S_F_L_C in
situations you wouldn’t expect (ex: paging writes) thats really whats
going on. The operation will be retried.

-----Original Message-----
From: Neil Weicher [mailto:xxxxx@netlib.com]
Sent: Thursday, October 19, 2000 3:53 PM
To: File Systems Developers
Subject: [ntfsd] STATUS_FILE_LOCK_CONFLICT vs STATUS_LOCK_NOT_GRANTED?

Does anyone know the difference between STATUS_LOCK_NOT_GRANTED and
STATUS_FILE_LOCK_CONFLICT?

Thanks.

Neil