From nobody Sat Dec 2 11:58:14 2023 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sj7jg4rPfz53BHp for ; Sat, 2 Dec 2023 11:58:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sj7jg3k3Gz4RWP for ; Sat, 2 Dec 2023 11:58:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1701518295; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=71kh/eV3oAGocQPu75F8e5pfppLExoZbXziulXBxVPg=; b=YNdYSSFTfWs98jLhiY9xZOUaqM+hQnE6aicGL0xgOMEVR1NITkepnjk0KYgGsgBSIHqowx 32eDILZqeFjiYHEqmC4ZPxPrwDTlXWGlk4FrCyaQQ3FAzhf95BMvdK0vYvYuDbvGYnGsZn PyC90HPweUdzClDHiYM3PmK+fvwZdCuffzClm/En/xeA+21HBpcoIcVbcZiZ2M36qjaMAS RQlfnBKEjsZKxdrjfnbsOTh+q1LGLx6c5AinGk0aMWNsuC1ebBm6Ko7r+9KkxhDeYevjQ7 Cpqodxe1vM0vO/CIqzTUhgXhCMGY6MFNcyZnwBbNwsxH7EtRR+jl68kqg7c+Xw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1701518295; a=rsa-sha256; cv=none; b=QV8AWhOQX4HgsaHgztgP8bO8R0D5npWDmnzc+8BWhw2F4z1R5yuu+Kt2QjQEf/8miXSJ5v NU26IHKX/A92yaOqbcI08Jdjr2krWsVP1RIQvOml1hHgF7htiJZamJE4/ZBFaEO3Un1p+7 lgcKS+nnqLnD6+tck8n7OMsFmwm0rsNKB71tbWuNYOxGFdfo4vQT0/guYgApoPP2YOknjA Ut+xSO0yDQF+d7vE7RXELHBaEcSRovK9MuteybVK4gZ1K5V7j1UqMXpvAcEJjw4N6HJU3d A36VJ3MUjNTsFOGPTb8ymn9or4R0c5UeM8VTg+VbCwa2fy5lzacGhpd5cC7OiQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Sj7jg2gxRz1rR for ; Sat, 2 Dec 2023 11:58:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 3B2BwFKC027895 for ; Sat, 2 Dec 2023 11:58:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3B2BwFv9027894 for bugs@FreeBSD.org; Sat, 2 Dec 2023 11:58:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275483] accessing stalled smbfs mount caused kernel panic Date: Sat, 02 Dec 2023 11:58:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: 000.fbsd@quip.cz X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275483 Bug ID: 275483 Summary: accessing stalled smbfs mount caused kernel panic Product: Base System Version: 13.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: 000.fbsd@quip.cz We have 8 machines in a LAN, all of them have mounted 3 smbfs shares from o= ne Windows server which became unavailable for a few days. Plus couple of smbfs mounts from another Windows machines (without any problem at this time) The= re were long timeouts accessing the mountpoints in /mnt/ but everything was stable. Once the network issue of problematic Windows machine was resolved,= I tried to umount and mount one of the problematic smbfs share on one machine which went good but I did not touch other stalled mounts on other machines.= All machines paniced at night at 3 AM when periodic daily scripts start to check the system, mounts etc. All machines have the same message logged: Fatal trap 12: page fault while in kernel mode cpuid =3D 7; apic id =3D 0e fault virtual address =3D 0x0 fault code =3D supervisor write data, page not present instruction pointer =3D 0x20:0xffffffff82384293 stack pointer =3D 0x28:0xfffffe0140dcbd40 frame pointer =3D 0x28:0xfffffe0140dcbde0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 1933 (smbiod5) trap number =3D 12 panic: page fault cpuid =3D 7 time =3D 1701482461 KDB: stack backtrace: #0 0xffffffff80c53f45 at kdb_backtrace+0x65 #1 0xffffffff80c068c1 at vpanic+0x151 #2 0xffffffff80c06763 at panic+0x43 #3 0xffffffff810b1fa7 at trap_fatal+0x387 #4 0xffffffff810b1fff at trap_pfault+0x4f #5 0xffffffff81088fe8 at calltrap+0x8 #6 0xffffffff82384a49 at smb_iod_sendrq+0x129 #7 0xffffffff82385139 at smb_iod_sendall+0xb9 #8 0xffffffff82385b56 at smb_iod_thread+0x156 #9 0xffffffff80bc314e at fork_exit+0x7e #10 0xffffffff8108a05e at fork_trampoline+0xe Uptime: 9d5h56m26s Dumping 2259 out of 29662 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..= 91% Dump complete I am curious why the machines paniced after the issue was fixed. The machines are all the same configuration =3D FreeBSD 13.2-p5 amd64 with GENERIC kernel. One share is mounted: smbfs, noexec, nosuid, read-only Other two: smbfs, noexec, nosuid --=20 You are receiving this mail because: You are the assignee for the bug.=