Project

General

Profile

Actions
Copy link

Bug #13826

closed

lofi: delayed mapping deletion can panic due to NULL ls_stacked_vp

Added by Toomas Soome about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Toomas Soome
Category:
driver - device drivers
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
1512

Description

panic message: BAD TRAP: type=e (#pf Page fault) rp=fffffe0008a20420 addr=28 occurred in module "genunix" due to a NULL pointer dereference

::stack

vnodetopath_common+0x290(0, 0, fffffe06623b2554, 400, fffffe065bb1a810, 0)
vnodetopath+0x24(0, 0, fffffe06623b2554, 400, fffffe065bb1a810)
lofi_get_info+0x191(8100000000, 80457dc, 4c4605, fffffe065bb1a810, 100401)

When mapping is deleted while still in use (lofiadm -d -f) the mapping will be removed, ls_stacked_vp is set to NULL and if we now call vnodetopath(), the system will panic.

Testing done: confirmed, we do not get panic any more.

Actions
Copy link

Also available in: Atom PDF