Age | Commit message (Collapse) | Author |
|
|
|
|
|
VCB_RO_COMPAT_READ_ONLY is a new flag to indicate that the volume
must be treated read-only due to unsupported RO_COMPAT features
being turned on.
|
|
|
|
Implement ro_compat/incompat flags inspection as a fix for #6.
|
|
|
|
|
|
If Ext2InitializeVcb() fails, Vcb->FcbLock may not be deinitialized.
|
|
|
|
|
|
always use buffer-head, to avoid possbible deadlock and multiple mappings
|
|
|
|
|
|
|
|
possible deadlock with Cc(Map/Pin/PreparePinWrite...) operations
upon Vcb->Volume stream fileobj
|
|
|
|
|
|
No doing volume flush when group description buffer headers
are already constructed (upon BCB internal eresource lock)
|
|
|
|
|
|
With outstanding BCBs, cache manager will try to grab BCB
resource before doing the actual flushing, thus cuase hang
|
|
When file does exist but doesn't match the requested file
attribute, Ext2Fsd should stop the search and then return
FILE/PATH-NOT-FOUND or IS_DIR or NOT_DIR error to system.
|
|
|
|
|
|
|
|
|
|
file system drivers don't care.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Fix duplicated call to Ext2MapUserBuffer
- Remove Ext2MapUserBuffer routine, use Ext2GetUserBuffer instead
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Do not check UserEaList in Ext2QueryEa
- Set XattrRefAcquired to TRUE when ext4_fs_get_xattr_ref succeeds
|