https://git.reactos.org/?p=reactos.git;a=commitdiff;h=4ef08871ee67cafc1b3566...
commit 4ef08871ee67cafc1b3566f408bd4f7a86df9a80 Author: Pierre Schweitzer pierre@reactos.org AuthorDate: Sun Dec 17 23:30:58 2017 +0100
[NTOSKRNL] Make again an attempt at killing the IopParseDevice() hack.
For the record, the only place it was remaining was 1st stage, notably because FSD (FastAT <3) was missing a few features. As this features weren't triggered in 3rd stage (unless forced), it was not needed there any longer.
Now that they are implemented, and seem working out of the box, this hack might not be longer anymore.
This is my ... ?! pfff attempt at killing it. It might not be the last, so just disabling the hack for now. If there are no regressions (who can really believe that?) we'll be clear for dropping it once for all. --- ntoskrnl/io/iomgr/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ntoskrnl/io/iomgr/file.c b/ntoskrnl/io/iomgr/file.c index 71863ccb42..11ad0529b3 100644 --- a/ntoskrnl/io/iomgr/file.c +++ b/ntoskrnl/io/iomgr/file.c @@ -533,7 +533,7 @@ IopParseDevice(IN PVOID ParseObject, /* Check if we can simply use a dummy file */ UseDummyFile = ((OpenPacket->QueryOnly) || (OpenPacket->DeleteOnly));
-#if 1 +#if 0 /* FIXME: Small hack still exists, have to check why... * This is triggered multiple times by usetup and then once per boot. */
-
Pierre Schweitzer