History log of /reactos/ntoskrnl/io/iomgr/iofunc.c (Results 1 – 25 of 49)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# c9864da8 22-Apr-2024 Timo Kreuzer <timo.kreuzer@reactos.org>

[NTOS:IO] Fix broken pool allocations

ExAllocatePoolWithTag doesn't raise an exception on failure, only ExAllocatePoolWithQuotaTag does. Use that when quotas are relevant instead of silently continu

[NTOS:IO] Fix broken pool allocations

ExAllocatePoolWithTag doesn't raise an exception on failure, only ExAllocatePoolWithQuotaTag does. Use that when quotas are relevant instead of silently continuing with a NULL pointer.

show more ...


Revision tags: 0.4.14-release
# 07e19a5e 24-Nov-2021 Eric Kohl <eric.kohl@reactos.org>

[NTOS:IO] Fail, if io completion port and an apc routine are used at the same time

Add checks to NtNotifyChangeDirectoryFile, NtLockFile, NtReadFile and NtWriteFile.
This fixes two ntdll tests.


# 34f2b783 28-Oct-2021 Thomas Faber <thomas.faber@reactos.org>

[NTOS:IO] Correctly deal with exceptions when handling FileFsDriverPathInformation. CID 1476847


# a74ff5be 28-Oct-2021 Thomas Faber <thomas.faber@reactos.org>

[NTOS:IO] Don't call IopCompleteRequest with uninitialized context values. CID 716761

NormalContext and NormalRoutine are just for good measure, but
SystemArgument2 is actually used by the function.

[NTOS:IO] Don't call IopCompleteRequest with uninitialized context values. CID 716761

NormalContext and NormalRoutine are just for good measure, but
SystemArgument2 is actually used by the function.
And yes, this appears to be a bug in Win 2003.

show more ...


# 9b1edcea 12-Sep-2021 Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org>

[REACTOS] Fix some instances of DPRINTs with trailing whitespace before newlines.


# 2d3454a8 04-Dec-2020 Jérôme Gardou <jerome.gardou@reactos.org>

[NTOS:IO] VFAT sucks less now


# ef4c7ae9 10-Dec-2020 Jérôme Gardou <jerome.gardou@reactos.org>

[NTOS:IO] Validate input parameters in NtQueryDirectoryFile

It turns out this is not the job of the FS driver


# a6c0af2e 18-Dec-2020 Jérôme Gardou <jerome.gardou@reactos.org>

[NTOS:IO] Do not pass bogus file offset to the FS in NtReadFile & NtWriteFile


Revision tags: 0.4.15-dev, 0.4.14-RC, 0.4.13-release, 0.4.14-dev, 0.4.13-RC, 0.4.12-release, 0.4.12-RC, 0.4.13-dev
# ef8b1a19 29-Mar-2019 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] We don't need an event if we don't issue an IRP


# 28ba29e4 29-Mar-2019 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Implement support for FileFsDriverPathInformation in NtQueryVolumeInformationFile


# 092c37f8 29-Mar-2019 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Do. Not. L. E. A. K.


# d75ccd01 28-Mar-2019 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Only allow direct device open for FileFsDeviceInformation


# ce6488df 28-Mar-2019 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Add a quick path for FileFsDeviceInformation in NtQueryVolumeInformationFile

This allows querying volume information without issuing an IRP to the owner device.
The kernel is supposed to

[NTOSKRNL] Add a quick path for FileFsDeviceInformation in NtQueryVolumeInformationFile

This allows querying volume information without issuing an IRP to the owner device.
The kernel is supposed to already have all the required information to return
to the caller.

Side effect: this allows querying volume information for devices not implementing
IRP_MJ_QUERY_VOLUME_INFORMATION such as null.sys
This fixes opening null device in Python.

Fix based on debugging by Maxim Smirnov in PR #1442

CORE-14551

show more ...


Revision tags: 0.4.11-release
# 63977328 19-Jan-2019 Thomas Faber <thomas.faber@reactos.org>

[NTOSKRNL] Guard against negative InformationClass enum values. CORE-15651


Revision tags: 0.4.11-RC, 0.4.12-dev, 0.4.10-release
# e19e907a 04-Oct-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Quickly check for alignment in NtRead/WriteFile

This quick check based on bits and operation is for 2^ based
sector sizes (most of the cases) and will perform faster than
the modulo opera

[NTOSKRNL] Quickly check for alignment in NtRead/WriteFile

This quick check based on bits and operation is for 2^ based
sector sizes (most of the cases) and will perform faster than
the modulo operation which is still used in fallback in case
the sector size wouldn't be a power of 2.

show more ...


# 44155053 04-Oct-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Use captured variable to check parameters in NtRead/WriteFile


# bf596690 04-Oct-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] On read/write, also check buffer respects device alignment requirements


# 1bd25c5c 04-Oct-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] When checking for byte offset alignment, tolerate some magic values


# fd334021 03-Oct-2018 Eric Kohl <eric.kohl@reactos.org>

[NTOSKRNL] NtReadFile/NtWriteFile: If a file has been opened for non-cached access, Length and ByteOffset must be sector size aligned.

This fixed two ntdll apitests.


# 15b9a6aa 03-Oct-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Call IoCreateFileSpecifyDeviceObjectHint with the hint if it was specified


# 8fbc4880 02-Oct-2018 Thomas Faber <thomas.faber@reactos.org>

[NTOS:IO] Implement IopAcquireFileObjectLock and use it to fix IopLockFileObject


Revision tags: 0.4.11-dev, 0.4.10-RC
# cf3b9d5b 29-Jul-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKNRL] Only allocate a MDL if we have an output length

For user mode, when probing output buffer, if it's null, length
will also be set to 0.

This avoids user mode applications being able to tr

[NTOSKNRL] Only allocate a MDL if we have an output length

For user mode, when probing output buffer, if it's null, length
will also be set to 0.

This avoids user mode applications being able to trigger various
asserts in ReactOS (and thus BSOD when no debugger is plugged ;-)).

show more ...


Revision tags: 0.4.9-release, 0.4.10-dev, 0.4.9-RC, 0.4.8-release
# a3c58ca7 24-Feb-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Implement the support for reserve IRP in IO

The reserve IRP is an IRP which is allocated on system boot and kept during
the whole system life. Its purpose is to allow page reads in case o

[NTOSKRNL] Implement the support for reserve IRP in IO

The reserve IRP is an IRP which is allocated on system boot and kept during
the whole system life. Its purpose is to allow page reads in case of
low-memory situations where the system doesn't have enough memory left
to allocate an IRP to read from the page file (would be catastrophic situation).

show more ...


# 9ac2e985 24-Feb-2018 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Add the CcDataFlushes and CcDataPages counters


Revision tags: 0.4.8-RC, 0.4.9-dev
# 9ecbbe2a 26-Nov-2017 Pierre Schweitzer <pierre@reactos.org>

[NTOSKRNL] Use ExAllocatePoolWithQuotaTag() when allocating SystemBuffer for the IRP
That way, in case the system lacks memory, an exception is thrown and IRP isn't sent
to the device with NULL Syste

[NTOSKRNL] Use ExAllocatePoolWithQuotaTag() when allocating SystemBuffer for the IRP
That way, in case the system lacks memory, an exception is thrown and IRP isn't sent
to the device with NULL SystemBuffer.

CORE-14048

show more ...


12