Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-9254

CD Filesystem ISO9660 BSOD on malformed ISO - "desktop.ini?"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 0.4.0
    • Component/s: Filesystems
    • Labels:
      None
    • Environment:

      ReactOS 0.4.0 build66430 2015-02-23 guest-OS
      within Microsoft Virtual PC 2007 SP2
      (VMware might be affected as well, didn't try)

      Description

      when you mount a corrupt ISO9660 iso (see attachment broken.iso) in MSVPC2007 as CD-ROM-drive and try to access from within explorer_new of reactos guest, you will reproducably get a BSOD
      within ntoskrnl.exe (see attachment brokenIsoCrash.png)

      (please note that a valid iso works as it is supposed to be in reactos)

      but when you try the same broken.iso within Win2K3 you get just a message box with text:
      "
      D:\ is not accessible.
      The file or directory is corrupted and unreadable.
      "

      Obviously Win2K3 still does a better job here
      Sanity check missing?

      Callstack:
      Assertion 'NumberOfBytes != 0' failed at /srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/expool.c line 1537

      Entered debugger on embedded INT3 at 0x0008:0x8095efd2.
      kdb:> bt
      Eip:
      <NTOSKRNL.EXE:15efd3 (:0 (DbgBreakPoint))>
      Frames:
      <NTOSKRNL.EXE:b444d (ntoskrnl/mm/ARM3/expool.c:1537 (ExAllocatePoolWithTag))>
      <NTOSKRNL.EXE:12d482 (ntoskrnl/rtl/libsupp.c:104 (RtlpAllocateMemory))>
      <NTOSKRNL.EXE:16a7ad (/mnt/ramdisk/buildbot/output-MinGW-i386/reactos/ReactOS/lib/rtl/unicode.c:1815 (RtlUpcaseUnicodeString))>
      <NTOSKRNL.EXE:57f4d (ntoskrnl/fsrtl/name.c:541 (FsRtlIsNameInExpression))>
      <cdfs.sys:3d07 (drivers/filesystems/cdfs/fcb.c:553 (CdfsDirFindFile))>
      <cdfs.sys:405a (drivers/filesystems/cdfs/fcb.c:697 (CdfsGetFCBForFile))>
      <cdfs.sys:1bf3 (drivers/filesystems/cdfs/create.c:156 (CdfsCreate))>
      <NTOSKRNL.EXE:7dd34 (ntoskrnl/io/iomgr/irp.c:1213 (IofCallDriver))>
      <NTOSKRNL.EXE:70935 (ntoskrnl/io/iomgr/file.c:858 (IopParseDevice))>
      <NTOSKRNL.EXE:113085 (ntoskrnl/ob/obname.c:809 (ObpLookupObjectName))>
      <NTOSKRNL.EXE:10ab52 (ntoskrnl/ob/obhandle.c:2504 (ObOpenObjectByName))>
      <NTOSKRNL.EXE:71e90 (ntoskrnl/io/iomgr/file.c:2457 (IoCreateFile))>
      <NTOSKRNL.EXE:72e33 (ntoskrnl/io/iomgr/file.c:3214 (NtCreateFile))>
      <NTOSKRNL.EXE:1476f0 (ntoskrnl/include/internal/i386/ke.h:689 (KiSystemServiceHandler))>
      <NTOSKRNL.EXE:3d95 (:0 (KiFastCallEntry))>
      <ntdll.dll:c761>
      <kernel32.dll:39348>
      <kernel32.dll:39f7a>
      <shell32.dll:3e5e2>
      <shell32.dll:274aa>--- Press q to abort, any other key to continue —
      <user32.dll:5898d>--- Press q to abort, any other key to continue —
      <user32.dll:59100>
      <browseui.dll:184c3>
      <kernel32.dll:19f8a>
      <00000000>

        Attachments

        1. broken.iso
          900 kB
        2. brokenISOcrash.PNG
          brokenISOcrash.PNG
          24 kB
        3. debug.log
          16 kB
        4. debuglog-Build 20150327-r66923.log
          120 kB
        5. KernelDebugViaSerial.log
          18 kB

          Activity

            People

            • Assignee:
              Heis Spiter Pierre Schweitzer
              Reporter:
              reactosfanboy reactosfanboy
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: