Opened 5 days ago
Last modified 5 days ago
#19122 new bug
PANIC: rw_lock_destroy(): read-locked and caller doesn't hold the write lock
| Reported by: | bbjimmy | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | File Systems/BFS | Version: | R1/beta5 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | #8405 | |
| Platform: | All |
Description
browsing https://arstechnica.com/ in WebPositive
Attachments (1)
Change History (4)
by , 5 days ago
| Attachment: | IMG_20240923_113442545.jpg added |
|---|
comment:1 by , 5 days ago
| Blocking: | 8405 added |
|---|---|
| Component: | System/Kernel → File Systems/BFS |
| Owner: | changed from to |
| Priority: | high → normal |
This is probably the real cause of #8405.
comment:2 by , 5 days ago
| Summary: | PANICK: rw_lock_destroy() → PANIC: rw_lock_destroy(): read-locked and caller doesn't hold the write lock |
|---|
comment:3 by , 5 days ago
Actually, I think this is a VFS bug and not a BFS bug. The VFS should keep references to vnodes that are currently performing asynchronous I/O.
Note:
See TracTickets
for help on using tickets.
screenshot of KDL