[Bug 257838] Garbage on a memory stick can cause GEOM raid taste g_raid_tr_iostart() to page-fault.

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 14 Aug 2021 15:43:16 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257838

            Bug ID: 257838
           Summary: Garbage on a memory stick can cause GEOM raid taste
                    g_raid_tr_iostart() to page-fault.
           Product: Base System
           Version: 13.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs_at_FreeBSD.org
          Reporter: rtm_at_lcs.mit.edu

Created attachment 227185
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=227185&action=edit
Causes a kernel page fault if placed at the end of a memory stick.

If I dd the attached data to the end of a memory stick, or run

  mdconfig -f si160.img

I get a kernel page fault on my 13.0-RELEASE-p3 machine:

GEOM_RAID: SiI-36f0f5d40c31: Array SiI-36f0f5d40c31 created.
GEOM_RAID: SiI-36f0f5d40c31: Disk md0 state changed from NONE to FAILED.
GEOM_RAID: SiI-36f0f5d40c31: Subdisk _at_aA¸sD|/s:0-md0 state changed from NONE to
FAILED.
GEOM_RAID: SiI-36f0f5d40c31: Array started.
GEOM_RAID: SiI-36f0f5d40c31: Volume _at_aA¸sD|/s state changed from STARTING to
SUBOPTIMAL.
GEOM_RAID: SiI-36f0f5d40c31: Provider raid/r0 for volume _at_aA¸sD|/s created.
GEOM_RAID: Warning! I/O request to an absent disk!
[unknown][READ(offset=12642167526035968, length=-12642167526035968)]
GEOM_RAID: Warning! I/O request to an absent disk! [unknown][READ(offset=0,
length=0)]
GEOM_RAID: Warning! I/O request to a disk in a wrong state (NONE)!
[unknown][READ(offset=0, length=0)]
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x78
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xffffffff80b618b8
stack pointer           = 0x0:0xfffffe0063d5aa80
frame pointer           = 0x0:0xfffffe0063d5aaa0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 725 (g_raid SiI-36f0f5d4)
trap number             = 12
panic: page fault
cpuid = 0
time = 1628953025
KDB: stack backtrace:
#0 0xffffffff80c57515 at kdb_backtrace+0x65
#1 0xffffffff80c09ef1 at vpanic+0x181
#2 0xffffffff80c09d63 at panic+0x43
#3 0xffffffff8108b1b7 at trap_fatal+0x387
#4 0xffffffff8108b20f at trap_pfault+0x4f
#5 0xffffffff8108a86d at trap+0x27d
#6 0xffffffff810619a8 at calltrap+0x8
#7 0xffffffff80b843a4 at g_raid_tr_iostart_concat+0x244
#8 0xffffffff80b62c70 at g_raid_worker+0x530
#9 0xffffffff80bc7e2e at fork_exit+0x7e
#10 0xffffffff81062a2e at fork_trampoline+0xe

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Sat Aug 14 2021 - 15:43:16 UTC

Original text of this message