[Bug 258477] panic: Assertion stp->st_flags == 0 failed (smbfs issue?)

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 13 Sep 2021 13:41:21 UTC

            Bug ID: 258477
           Summary: panic: Assertion stp->st_flags == 0 failed (smbfs
           Product: Base System
           Version: 13.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: arichardson@FreeBSD.org

With latest HEAD (base 41b0190cc404e21cb8b430602eabfedc20107471) I am seeing
the following panic during shutdown after running kyua tests and copying the
result to smbfs:

*** FINAL System shutdown message from root@freebsd-amd64 ***

System going down IMMEDIATELY

System shutdown time has arrived
Sep 13 13:36:47 freebsd-amd64 shutdown[81601]: power-down by root:
Stopping sshd.
Stopping rpcbind.
Stopping devd.
Writing entropy file: .
Writing early boot entropy file: .
Sep 13 13:36:47 freebsd-amd64 syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining... 1 1 lock order reversal:
 1st 0xfffff80003f5f230 syncer (syncer, lockmgr) @
 2nd 0xfffff80003b445b0 mntfs (mntfs, lockmgr) @
lock order syncer -> mntfs attempted at:
#0 0xffffffff80c830a4 at witness_checkorder+0xbe4
#1 0xffffffff80be2cc2 at lockmgr_lock_flags+0x182
#2 0xffffffff80d178c4 at _vn_lock+0x54
#3 0xffffffff80f39356 at ffs_sync+0x2e6
#4 0xffffffff80d0b36b at sync_fsync+0xeb
#5 0xffffffff80d087fc at sched_sync+0x42c
#6 0xffffffff80bcc170 at fork_exit+0x80
#7 0xffffffff810a195e at fork_trampoline+0xe
1 0 0 done
Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... done
All buffers synced.
panic: Assertion stp->st_flags == 0 failed at
cpuid = 0
time = 1631540211
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0093ceeb50
vpanic() at vpanic+0x17f/frame 0xfffffe0093ceeba0
panic() at panic+0x43/frame 0xfffffe0093ceec00
seltdfini() at seltdfini+0xa0/frame 0xfffffe0093ceec20
exit1() at exit1+0x488/frame 0xfffffe0093ceec80
kproc_exit() at kproc_exit+0xa9/frame 0xfffffe0093ceecb0
smb_iod_thread() at smb_iod_thread+0x354/frame 0xfffffe0093ceecf0
fork_exit() at fork_exit+0x80/frame 0xfffffe0093ceed30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0093ceed30
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 812 tid 100098 ]
Stopped at
      kdb_enter+0x37: movq    $0,0x1288f3e(%rip)

You are receiving this mail because:
You are the assignee for the bug.